Re: IMCC optimizer instruction duplication and opcode write/reads

On Dec 31, 2005, at 15:43, Amos Robinson wrote: I was wondering if anybody could help: the best I've found for duplicating an instruction is INS(interp, unit, ins->op, "", ins->r, ins->n_r, ins->keys, 0); A copy_ins() function would be nice, if needed. However, this doesn't seem to work

[perl #38116] [TODO] Tcl - provide a way to access PIR from Tcl

# New Ticket Created by Will Coleda # Please include the string: [perl #38116] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/rt3/Ticket/Display.html?id=38116 > While this is current doable via [inline], we should also be able to do this via [name

[perl #38117] [TODO] Tcl - implement [namespace]

# New Ticket Created by Will Coleda # Please include the string: [perl #38117] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/rt3/Ticket/Display.html?id=38117 >

[perl #38119] [TODO] Tcl - implement missing globals

# New Ticket Created by Will Coleda # Please include the string: [perl #38119] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/rt3/Ticket/Display.html?id=38119 > All globals mentioned in http://www.tcl.tk/man/tcl8.5/TclCmd/ tclvars.htm must be imple

[perl #38118] [TODO] namespace PDD

# New Ticket Created by Will Coleda # Please include the string: [perl #38118] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/rt3/Ticket/Display.html?id=38118 >

$/ and $! should be env (and explanation of env variables)

I propose that we change $! (formerly global) and $/ (formerly implicitly lexical) to being env variables. Here is the IRC conversation where Audrey convinced me: http://colabti.de/irclogger/irclogger_log/perl6?date=2006-01-01,Sun&sel=1213#l1893 Let me explain env variables, because my misunderst

Pugs-Rule: Grammar support.

Today I added two more rules in the default grammar, in addition to : rule p6namedrule     { rule \s+ ([\w|<'::'>]+) \s* \{ \} ;? \s* } rule p6grammar     { ^ grammar \s+ ([\w|<'::'>]+); \s* * $ } With this, the PILN grammar is now successfully parsed with its Syntax.grammar file.  To su

Rules should be independent of evaluation strategy

Recursive descent is slow, and it produces bad error messages unless you are very careful with your calls, but it is very flexible and (locally) predictable. Predictive parsing is faster and produces fantastic error messages, and is fairly flexible. Bottom up parsing is very flexible, but is ver

[perl #38114] [TODO] Tcl - Run tcltest.tcl

# New Ticket Created by Will Coleda # Please include the string: [perl #38114] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/rt3/Ticket/Display.html?id=38114 > The next *big* milestone is to be able to run tcl's test suite natively. That means be

[perl #38113] [TODO] partcl version 0.2

# New Ticket Created by Will Coleda # Please include the string: [perl #38113] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/rt3/Ticket/Display.html?id=38113 > Milestone ticket for any issues related to this partcl version

[perl #38115] [TODO] Tcl - read per user settings

# New Ticket Created by Will Coleda # Please include the string: [perl #38115] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/rt3/Ticket/Display.html?id=38115 > Handle ".tclshrc" or "tclshrc.tcl" as per: http://www.tcl.tk/man/ tcl8.5/UserCmd/tclsh.

Re: Cygwin versun plain XP (for working with Pugs+Parrot together)

The os.pmc issue is unrelated the issue with atan2(). It's pretty clear that Cygwin does have the POSIX vs. IEEE atan2() behavior issue. Thanks for confirming. -J -- On Sun, Jan 01, 2006 at 03:13:16PM -0600, Greg Bacon wrote: > In message <[EMAIL PROTECTED]>, > Joshua Hoblitt writes: > > :

Re: Rules should be independent of evaluation strategy

On Sun, Jan 01, 2006 at 07:15:46PM +, Luke Palmer wrote: > Recursive descent is slow, and it produces bad error messages unless > you are very careful with your calls, but it is very flexible > and (locally) predictable. Predictive parsing is faster and produces > fantastic error messages, an

[perl #38123] [TODO] build - change genfile() interpolation syntax

# New Ticket Created by Joshua Hoblitt # Please include the string: [perl #38123] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/rt3/Ticket/Display.html?id=38123 > Parrot::Configure::Step::genfile() currently interpolates values in the format ${foo}

[perl #38124] [TODO] build - header file detection w/o perl5

# New Ticket Created by Joshua Hoblitt # Please include the string: [perl #38124] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/rt3/Ticket/Display.html?id=38124 > auto::headers uses the Config module to detect installed header files. It's ok to get