On Fri, 6 Sep 2002, Mike Lambert wrote:
> t/compiler/8.t 1 256 61 16.67% 6
Good to know I can pass the buck on this one.
> t/compiler/a.t 1 256 31 33.33% 2
That sounds like P6C failing somewhere -- imcc parse errors typically are.
> t/rx/call.t1 256
> > In tracking down a gc bug, I realized that the current throwaway
> > implementation of the print op could be replaced with a faster
> > throwaway implementation that avoids doing a string_to_cstring.
> >
> > Note that both the original and new implementations are still buggy
> > with respect t
> Perl6 on Win32 MS VC++ gives:
>
> Failed TestStatus Wstat Total Fail Failed List of Failed
> --
>
> t/compiler/8.t 1 256 61 16.67% 6
> t/compiler/a.t 1 256 31 33.33% 2
> t/rx/call.t1 256
This is an interesting tidbit from a longer posting by Oren Ben-Kiki, the
YAML specification author. Thought I'd pass it on.
- Forwarded message from Oren Ben-Kiki <[EMAIL PROTECTED]> -
From: Oren Ben-Kiki <[EMAIL PROTECTED]>
Date: Thu, 5 Sep 2002 11:28:12 +0300
To: [EMAIL PROTECTED]
Sub
On Thu, 5 Sep 2002, Dan Sugalski wrote:
> At 1:40 PM +0100 9/5/02, Nicholas Clark wrote:
> >I believe applying the patch is the right thing, because it's progress
> >on where we are, but I think (not fully formed yet) that we would benefit
> >from finer granularity on what can get modified
>
>
Dan Sugalski wrote:
> At 8:04 AM + 9/5/02, Leopold Toetsch (via RT) wrote:
Argh, someone reverted the patch in CVS, when changing some "print"
functions.
Please, this is core.ops
>> core.ops has currently:
>>
>> - obvious errors e.g.
>> -inline op mul (out PMC, out PMC, out PMC) {
>
On Wed, Sep 04, 2002 at 10:46:24PM -0400, Ken Fox wrote:
> What is really needed is something that converts the date syntax
> to normal Perl code:
>
>rule iso_date { () -
>() -
>()
>{ use grammar Perl::AbstractSyntax;
>
On Thu, 5 Sep 2002, Jeff wrote:
> Ewps. It was recently pointed out to me that I accidentally reversed
> #17000. The problem has been fixed, I believe. Sorry, Andy.
That's ok, it's partly my fault too. I had posted the patch hoping for
comments, but grew impatient. I knew it was a decent band-
At 1:39 PM +0200 9/6/02, Josef Hook wrote:
>On Thu, 5 Sep 2002, Dan Sugalski wrote:
>
>> At 1:40 PM +0100 9/5/02, Nicholas Clark wrote:
>> >I believe applying the patch is the right thing, because it's progress
>> >on where we are, but I think (not fully formed yet) that we would benefit
>> >f
Nicholas Clark <[EMAIL PROTECTED]> writes:
> On Wed, Sep 04, 2002 at 10:46:24PM -0400, Ken Fox wrote:
>> What is really needed is something that converts the date syntax
>> to normal Perl code:
>>
>>rule iso_date { () -
>>() -
>>()
>>
On Fri, Sep 06, 2002 at 01:34:56AM -0400, Aaron Sherman wrote:
> # INTERNAL q, qq, qw
> # XXX - how do I do quote-like operators? I know I saw someone say...
> # Need to do: qr (NEVER("qr")) and qx
presumably the way the perl5 tokeniser does them - by parsing the string
into a series of concaten
On Fri, Sep 06, 2002 at 02:20:10PM +0100, Piers Cawley wrote:
> Nicholas Clark <[EMAIL PROTECTED]> writes:
>
> > On Wed, Sep 04, 2002 at 10:46:24PM -0400, Ken Fox wrote:
> >> What is really needed is something that converts the date syntax
> >> to normal Perl code:
> >>
> >>rule iso_date { (
Nicholas Clark <[EMAIL PROTECTED]> writes:
> On Fri, Sep 06, 2002 at 02:20:10PM +0100, Piers Cawley wrote:
>> Nicholas Clark <[EMAIL PROTECTED]> writes:
>>
>> > On Wed, Sep 04, 2002 at 10:46:24PM -0400, Ken Fox wrote:
>> >> What is really needed is something that converts the date syntax
>> >> t
On Fri, Sep 06, 2002 at 02:34:52PM +0100, Nicholas Clark wrote:
> On Wed, Sep 04, 2002 at 10:46:24PM -0400, Ken Fox wrote:
> > What is really needed is something that converts the date syntax
> > to normal Perl code:
> >
> >rule iso_date { () -
> >() -
> >
On Fri, 2002-09-06 at 09:29, Nicholas Clark wrote:
> On Fri, Sep 06, 2002 at 01:34:56AM -0400, Aaron Sherman wrote:
>
> > # INTERNAL q, qq, qw
> > # XXX - how do I do quote-like operators? I know I saw someone say...
> > # Need to do: qr (NEVER("qr")) and qx
>
> presumably the way the perl5 toke
On Fri, Sep 06, 2002 at 02:49:13PM +0100, Piers Cawley wrote:
> Nicholas Clark <[EMAIL PROTECTED]> writes:
> > This idea of just switching language syntax in a context-sensitive way is
> > trying to make my head explode.
>
> But you mean that in a good way right? Anyway, he did introduce the
Ye
Has anyone tried kcachegrind to speed profile parrot? Based on what the web
page http://www.weidendorfers.de/kcachegrind/ says:
The trace includes the number of instruction/data memory accesses and
1st/2nd level cache misses, and relates it to source lines and functions
of the run pr
I've been told that my patch #16937 (which changes ld_shared from the
hard-wired wrong value of -shared to $Config{lddlflags}, which is the
variable designed in perl5 for this precise use) breaks cygwin. But in
the current state of affairs, without this patch, every other build that
doesn't use G
Ken Fox wrote:
> Excellent. Will there be an abstract syntax for tree
> rewriting or is it Perl 6 all the way down?
I'd expect it to be Perl all the way down. Though a
tree rewriting module might make it seem abstract. ;-)
> This is really amazing stuff. I was expecting some
> support for
#17026 was reverted by committing minor print changes.
Please clean up the mess, whoever did it.
leo
On Fri, Sep 06, 2002 at 09:01:13PM +0200, Leopold Toetsch wrote:
> #17026 was reverted by committing minor print changes.
>
> Please clean up the mess, whoever did it.
It has been reverted, but not in the way you describe:
revision 1.208
date: 2002/09/06 07:26:22;
Sorry for bothering again.
The impact of this ticket might not be clear to all people.
Platform
* All
Severity
* High (tending to fatal WRT imcc[1] & perl6)
Tag
* core
Patch Status* Reverted innocently by someone
I have no permission to change status of #17026 to above.
[1] fatal
I guess I'll brave the chaos...
Ok, I have undone the accidental reversion.
Leo, can you send me the patch and ChangeLog? I'd rather have Melvin
commit it, but I was just trying to get something to work with imcc
and I won't bother if you've already fixed it.
Also:
On Sat, Sep 07, 2002 at 12:2
# New Ticket Created by Steve Fink
# Please include the string: [perl #17065]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt2/Ticket/Display.html?id=17065 >
Apply as much or as little of this patch as you want.
- Add a few more patterns to vario
On Sat, 7 Sep 2002, Steve Fink wrote:
> Apply as much or as little of this patch as you want.
Looks good to me.
> - Add a few more patterns to various .cvsignore files
> - Add a -e (or --eval) flag to perl6.
For those "quick" one-liners?
> - Reindent a bunch of code that had too few spaces
> -
On Thu, 5 Sep 2002, Andy Dougherty wrote:
> Ok, with the alignment hack now in (see resources.c) and lots of various
> and sundry portability fixes, it looks like we're on our way to turning
> the tinderbox a lovely shade of green.
AARGH! It appears I spoke too soon. I don't have easy access t
applied, thanks.
/s
On Fri, Sep 06, 2002 at 06:01:20PM -0700, Sean O'Rourke wrote:
> On Sat, 7 Sep 2002, Steve Fink wrote:
>
> > - Add a -e (or --eval) flag to perl6.
>
> For those "quick" one-liners?
For running things under the debugger. It's easier to mess with
@DB::ARGS than it is to play around with external
On Fri, Sep 06, 2002 at 09:32:27PM -0400, Andy Dougherty wrote:
> On Thu, 5 Sep 2002, Andy Dougherty wrote:
>
> > Ok, with the alignment hack now in (see resources.c) and lots of various
> > and sundry portability fixes, it looks like we're on our way to turning
> > the tinderbox a lovely shade o
On Fri, 6 Sep 2002, Steve Fink wrote:
> > > - Make sure P6C::IMCC::code() adds a newline after every line
> > > (I was getting two consecutive lines of code smashed together)
> >
> > This will probably make the output pretty ugly. I'd rather find the
> > culprit for the smashed-together lines,
On Fri, Sep 06, 2002 at 08:09:21PM -0700, Sean O'Rourke wrote:
> On Fri, 6 Sep 2002, Steve Fink wrote:
> > > > - Make sure P6C::IMCC::code() adds a newline after every line
> > > > (I was getting two consecutive lines of code smashed together)
> > >
> > > This will probably make the output prett
Question #1:
If \n matches any one of the platform-specific newline character
sequences, does that mean that if I have a string like this[*]:
"foo bar baz\rfoo bar baz\nfoo bar bar\r\n"
that \n will match in 3 places? How do you tell perl that you only
want \n to match a specific newl
Answering to the best of my knowledge.
On Sat, 7 Sep 2002, Jonathan Scott Duff wrote:
> Question #2:
>
> Why are we storing the hypothetical's sigil in the match object?
I think it's to differentiate the different namespaces (scalar, array,
hash) within the match object's hash. Personally,
33 matches
Mail list logo
