> Elapsed times for 'time parrot hanoi.pbc 14 > /dev/null' are:
> CVS: 52.81, 52.05, 52.33
> CVS + grey COW: 51.53, 52.06, 51.67
> CVS + Mike's COW: 44.31, 44.48, 44.55
> CVS + grey1: 35.89, 36.48, 36.60 (+COW +cyclecount -stackwalk)
> End June grey: 30.14, 29.35, 29.53
>
> And 5000 generations of
In message <[EMAIL PROTECTED]>
Mike Lambert <[EMAIL PROTECTED]> wrote:
> - assemble.pl:
> shouldn't the code :
> elsif ($_->[0] =~ /^([snpk])c$/) { # String/Num/PMC/Key constant
> include support for "kic" somewhere?
It doesn't need to as to_bytecode() turns [1] into an ic argu
[EMAIL PROTECTED] wrote:
> [...] whose type is simultaneously C and C.
Has any thought yet gone into the builtin Perl types and what they will
be called in Perl 6? Will there be a difference between the C of
something and the type(s) that C returns?
In keeping with the lower case C and C exa
If anyone is interested, I've hacked together a Parrot tokenizer ... the
main intention for it was to form the basis of a syntax highlighter, but
I'm sure someone will find more creative applications for it...
I hacked together a very quick and dirty syntax highlighter (about 10
lines) using t
Peter Sergeant wrote:
> If anyone is interested, I've hacked together a Parrot tokenizer ... the
> main intention for it was to form the basis of a syntax highlighter, but
> I'm sure someone will find more creative applications for it...
To clarify: it's actually a PASM tokenizer...
+Pete
# New Ticket Created by Jarkko Hietaniemi
# Please include the string: [perl #16283]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt2/Ticket/Display.html?id=16283 >
Tru64 finds the following objectionable spots from a fresh CVS checkout:
cc: Warn
Mike Lambert wote:
> Run languages/basic/basic.pl.
> Type "LOAD WUMPUS, and hit return.
> Type "RUN", and hit return.
> Type "N" and hit return.
The thot plickens!
My results for the above are:
Interpreter version Time Data size
CVS8s1320kB
CVS +
On Sun, Aug 18, 2002 at 02:35:09PM +, Jarkko Hietaniemi wrote:
>
> Tru64 finds the following objectionable spots from a fresh CVS checkout:
Does this patch fix it? (Though even if it does, I wouldn't be at all
surprised if some other compiler choked on it.)
Index: rx.ops
===
It also reverts my bugfix for missing the first PMC allocated. I have
re-applied the fix.
# New Ticket Created by Steve Fink
# Please include the string: [perl #16286]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt2/Ticket/Display.html?id=16286 >
Enclosed is a patch for my best guess as to how to implement the
--debugging flag to Conf
Tim Bunce wrote:
>>Personally, I'm deprecating "regex" and its variants in my own writing and
>>speaking, and trying to stick to "rule" and "pattern".
>
>
> Using "pattern" in general and "rule" in the context of a grammar?
Using "pattern" for the contents and "rule" for the container.
But no
Trey Harris asked:
> Another one...
>
> class Foo is Bar;
>
> method a {
> setup();
> }
>
> 1;
> # EOF
>
> (Is the 1 still required?
No.
> I think I heard Damian say it was going away.)
Yes.
> The question is, is this valid, if Bar defines a sub/static method
> 'setup'?
If C is a C,
> The thot plickens!
Unforunately...yes. :)
> My results for the above are:
> Interpreter version Time Data size
> CVS8s1320kB
> CVS + ML COW 20s 19172kB
> CVS + Grey15s1884kB
> CVS + ML COW - re
Trey Harris wrote:
> Then I'd assume that multiple inheritance of both types would also
> conform?
Yes.
> So if $! is Errno, where class Errno is str is int
> that would work too?
I very much doubt you'll be able to inherit from the builtin types.
> (or is that Errno is str, int?),
M
Okay, here's two new vtable methods
freeze(PMC) - Responsible for freezing a PMC to the current freeze
data stream. Throws an exception on error
thaw(PMC) - A class method that thaws a PMC from the current thaw data stream
Both of these should use the freeze/thaw API--I'll get that defin
Here are some timings on my system with your basic stats patch:
These results are taken when the first command input is expected,
having keyed-ahead the N to avoid delays.
CVS + COW: (using your original cow patch)
Took 36.080085 seconds. A total of 2412496 bytes were allocated
A total of 18 DOD
> The following patch eliminates an alignment warning in packfile.c, and
> adds a comment to packfile.h about alignment assumptions underlying the
> size of the packfile header.
Applied, thanks.
> I wonder if we ought to have a Configure "sanity section" wherein various
> assumptions are tested
One thing that might be worth noting is that the current CVS version does do
some "unintended" COW things. My previous patch (the RECALL -> AGAIN) thing
attempted to fix this but has not been applied. Basically, when setting a
value that was previously a non-string value (integer, float, etc...)
> In the quest for removing warnings, I added an option --ccwarn to
> Configure.pl. With this option I could selectivly turn on and off
> warnings, and especially compile with -Werror, so I don't miss any
> warnings. The simple warnings (the missing return values) were already
> fixed before I was
On Sat, Aug 17, 2002 at 03:58:32PM -0700, Brent Dax wrote:
> =head2 Strings
>
> Parrot-level Cs are to be represented by the type
> C. This type is defined to be a pointer to a C parrot_string_t>.
>
> The functions for creating and manipulating Cs are listed
> below.
Is it worth arranging a r
Nicholas Clark:
# > The functions for creating and manipulating Cs are
# > listed below.
#
# Is it worth arranging a reminder in here that as parrot is
# garbage collected there is no confusion about who owns
# pointers to blah?
Probably. (Actually, I'd probably put it in a section above thi
On Sun, Aug 18, 2002 at 05:23:23PM -, Steve Fink wrote:
> On Sun, Aug 18, 2002 at 02:35:09PM +, Jarkko Hietaniemi wrote:
> >
> > Tru64 finds the following objectionable spots from a fresh CVS checkout:
>
> Does this patch fix it? (Though even if it does, I wouldn't be at all
> surprised
> > > Tru64 finds the following objectionable spots from a fresh CVS checkout:
> >
> > Does this patch fix it? (Though even if it does, I wouldn't be at all
> > surprised if some other compiler choked on it.)
>
> Works okay in Tru64 and IRIX which are known for their pointer pickiness.
Applied, t
> Here are some timings on my system with your basic stats patch:
> These results are taken when the first command input is expected,
> having keyed-ahead the N to avoid delays.
Technically, the patch I gave you doesn't count the delay waiting for user
input. But there are other things to discuss
On 18/08/02 16:06 -0400, Dan Sugalski wrote:
> Okay, here's two new vtable methods
>
>freeze(PMC) - Responsible for freezing a PMC to the current freeze
> data stream. Throws an exception on error
>
>thaw(PMC) - A class method that thaws a PMC from the current thaw data stream
>
> Both
25 matches
Mail list logo
