# New Ticket Created by jerry gay
# Please include the string: [perl #38260]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/rt3/Ticket/Display.html?id=38260 >
attached is my lib/Parrot/Config.pm file generated from r11223, on
windows using msvc. ins
# New Ticket Created by Matt Fowles
# Please include the string: [perl #38261]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/rt3/Ticket/Display.html?id=38261 >
Bob~
On 1/15/06, Leopold Toetsch <[EMAIL PROTECTED]> wrote:
>
> On Jan 14, 2006, at 21:
# New Ticket Created by Bob Rogers
# Please include the string: [perl #38264]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/rt3/Ticket/Display.html?id=38264 >
The attached code compiles to byte code OK in r11235, until you
comment out the push_e
# New Ticket Created by Bob Rogers
# Please include the string: [perl #38263]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/rt3/Ticket/Display.html?id=38263 >
From: Matt Fowles <[EMAIL PROTECTED]>
Date: Tue, 17 Jan 2006 16:29:55 -0500
Bob
# New Ticket Created by jerry gay
# Please include the string: [perl #38262]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/rt3/Ticket/Display.html?id=38262 >
perl modules necessary for parrot configuration, development, and
testing have been either
From: Matt Fowles <[EMAIL PROTECTED]>
Date: Tue, 17 Jan 2006 16:29:55 -0500
Bob~
On 1/15/06, Leopold Toetsch <[EMAIL PROTECTED]> wrote:
>
> On Jan 14, 2006, at 21:28, Bob Rogers wrote:
>
> >I had thought this field was being used, but it turns out to be
> > irreleva
On Jan 17, 2006, at 18:01, Andrew Rodland wrote:
Doesn't that imply that "print print print print 1;" is a valid Punie
program? Is that intentional? It seems to me that the gprint rule
should instead contain "cexpr":
rule gprint { (print) \s* }
"print print print print 1;" is certainly
On Tuesday 17 January 2006 15:01, Andrew Rodland wrote:
> "print print print print 1;" is certainly a valid Perl 5 program; it
> prints a 1 followed by 3 other things (which are defined to be true, and
> which happen to also be the number 1).
Nit: print doesn't *always* return a true value. It'
On Tuesday 17 January 2006 16:50, Chris Dolan wrote:
> Allison et al.,
>
> I was looking at languages/punie/lib/punie.g in the current SVN head
> and got confused. I see:
>rule gprint { (print) \s* }
> and
>rule expr{ | }
>
> Doesn't that imply that "print print print print 1;" is
Allison et al.,
I was looking at languages/punie/lib/punie.g in the current SVN head
and got confused. I see:
rule gprint { (print) \s* }
and
rule expr{ | }
Doesn't that imply that "print print print print 1;" is a valid Punie
program? Is that intentional? It seems to me that
Bob~
On 1/15/06, Leopold Toetsch <[EMAIL PROTECTED]> wrote:
>
> On Jan 14, 2006, at 21:28, Bob Rogers wrote:
>
> >I had thought this field was being used, but it turns out to be
> > irrelevant. I offer this patch so that no one else is fooled (and
> > because I had to test it anyway to prove
> [jonathan - Sa 14. Jan 2006, 09:57:37]:
> > I propose to rename 'src/classes' to 'src/pmc' as IMHO it makes
> > more sene. 't/pmc' is already named 'pmc'.
> >
> Yes, and for consistency please also rename dynclasses to dynpmc and the
> t/dynclass to t/dynpmc.
The first step, renaming 'src/dync
It looks like the script 'tools/dev/genrpt.pl' does basically the same as
'parrotbug'.
In order to decrease the level of confusion I propose to remove
genrpt.pl and the associated make targets 'ok', 'okfile', 'nok', 'nokfile'.
CU, Bernhard
On Tue, Jan 17, 2006 at 08:28:37AM -0600, Greg Bacon wrote:
: I'm still seeing a link failure with r11221.
:
: A confusing bit: I stopped the stripping of libparrot.dll, and nm
: seems to see the symbols that the linker's complaining about:
:
: [...]
: Compiling with:
: xx.c
: gcc -I./include -pi
I'm still seeing a link failure with r11221.
A confusing bit: I stopped the stripping of libparrot.dll, and nm
seems to see the symbols that the linker's complaining about:
[...]
Compiling with:
xx.c
gcc -I./include -pipe -I/usr/local/include -g -Wall -Wstrict-prototypes
-Wmissing-prototypes -Wi
15 matches
Mail list logo
