On Wednesday 23 May 2007 18:06:38 Will Coleda wrote:
> I confess to not grasping the point you claim is simple. As you
> understand it, what is there about a register based machine, as
> opposed to a stack based machine, that specifically improves the
> performance of operating on dynamically typ
A reply from the anonymous colleague.
I pass it along as presented to me, unaltered except for this prelude.
Note that while these are not *my* questions, I find both the
original questions and the followups compelling and in need of
answering.
I hope that we can get some of the design tea
On Wednesday 23 May 2007 13:29:26 Mark Glines wrote:
> I think the test should only run if a file named "DEVELOPING" exists,
> just like the codingstd tests do.
Agreed.
Thanks, applied as r18635.
-- c
# New Ticket Created by Mark Glines
# Please include the string: [perl #43041]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=43041 >
This test apparently tries to call svn/svk to query the mime-type of
the various source f
Am Mittwoch, 23. Mai 2007 15:26 schrieb Andy Dougherty:
> /*
> * These constants correspond to the debugger commands and are
> * used in src/debug.c. To map command strings to their
> * numeric values, use the algorithm from parse_command() in that file.
> */
>
> #define c_b 25245
Am Mittwoch, 23. Mai 2007 04:05 schrieb Patrick R. Michaud:
> Here's the perl 6 code:
>
> my $a = sub { ... }; # $a is a subroutine reference
> my $b := $a;
> # ...;
> $a = 4; # $a is now an Int
>
> How to do the above in PIR if we can't morph a Sub?
I may be
On Wed, 23 May 2007, Klaas-Jan Stol wrote:
> > There are some magic numbers, like 255, and some other very unclear code
> > snippets like:
> >
> > for (i = 0; *command && isalpha((int) *command); command++, i++)
> > c += (tolower((int) *command) + (i + 1)) * ((i + 1) * 255);
> >
> >
>
On 5/23/07, Klaas-Jan Stol <[EMAIL PROTECTED]> wrote:
On 5/23/07, chromatic <[EMAIL PROTECTED]> wrote:
>
> This file implements most of the Parrot debugger. The interpreter
> struct has
> a slot called pdb that contains a PDB_t (parrot/debug.h).
>
> This file is somewhat messy. It has some s
On 5/23/07, chromatic <[EMAIL PROTECTED]> wrote:
This file implements most of the Parrot debugger. The interpreter struct
has
a slot called pdb that contains a PDB_t (parrot/debug.h).
This file is somewhat messy. It has some string manipulation functions
(nextarg(), skip_ws(), parse_int(), pa
