On Fri, Aug 30, 2002 at 03:49:07PM -0400, Andy Dougherty wrote:
> By default, traditional yacc puts its output files in y.tab.[ch]. Thus
> my imcc/Makefile currently has
>
> $(YACC) -d -v imcc.y
> mv y.tab.c imcparser.c
> mv y.tab.h imcparser.h
>
> That's no problem, and works
On Sat, 31 Aug 2002, Leopold Toetsch wrote:
> > ... make the barrier to running languages/perl6 as low as possible,
>
> > By default, traditional yacc puts its output files in y.tab.[ch]. Thus
> > my imcc/Makefile currently has
> >
> > $(YACC) -d -v imcc.y
> > mv y.tab.c imcparser.c
>
libparrot.a is not really related to testing, it should belong in "all". This
patch does so, and as a side effect, t/src/basic will now work with "make testj".
__
Do You Yahoo!?
Yahoo! Finance - Get real-time stock quotes
http://finance.yahoo.com
-
Leopold Toetsch wrote:
> $ perl6 -k examples/life-ar.p6 5
> Running generations
This problem is due to the fact that the argument strings are
created with the external flag set, which is not properly
supported by the string and GC modules. Steve posted
some patches recently that might well fix
Andy Dougherty wrote:
> ... make the barrier to running languages/perl6 as low as possible,
My concerns too.
(Some history)
- I sent all the patches to get P6C running with 5.005_03
- I'm currently 95% maintaining/pushing the per6 driver (perl6)
- last ~50 Kb imcc patches originated from my
On Thu, Aug 29, 2002 at 07:35:46PM +, Steve Fink wrote:
> This patch makes re-running Configure.pl avoid updating the timestamps
> on the generated .h (and many other) files iff the files did not
> actually change. This is really only helpful to people who are working
> on the Configure system
On Thu, 29 Aug 2002, Melvin Smith wrote:
> I can live with the warning, as long as it compiles under traditional
> lex and flex. Don't waste too much effort polishing imcc since it will be
> getting a new interface eventually and might even be rewritten to self-host
> on Parrot at some point. (He
# New Ticket Created by Andy Dougherty
# Please include the string: [perl #16884]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt2/Ticket/Display.html?id=16884 >
This one seems to have fallen through the cracks. Here's a re-send.
--- parrot-orig
Leon Brocard (via RT) wrote:
> I have a weird bug where concatenation is sometimes failing, and I
> have no idea why. See the attached pasm. I fully expect both works and
> weird to output "foo", "bar", "quux" with various levels of spacing,
> but weird doesn't output quux.
Patch below should fi
> I have a weird bug where concatenation is sometimes failing, and I
> have no idea why.
> ...
While trying to find shortest code which reproduces this, I found
probably related bug where string is overwritten by a constant in
memory.
set S0, ""
set S1, "ABCDEFGHIJK"
set S2, "123456789012"
co
On Fri, Aug 30, 2002 at 08:35:43AM +, [EMAIL PROTECTED] wrote:
> # New Ticket Created by Leon Brocard
> # Please include the string: [perl #16874]
> # in the subject line of all future correspondence about this issue.
> # http://rt.perl.org/rt2/Ticket/Display.html?id=16874 >
>
>
> Hi.
>
Steve Fink wrote:
> On Thu, Aug 29, 2002 at 11:56:42PM +0200, Leopold Toetsch wrote:
> The script you're referring to sounds like it actually does something
> meaningful, like run ops2c.pl on all the tests and execute them that
> way.
s/ops2c.pl/pbc2c.pl/perl6/ ;-)
> ... Which is utterly un
> I have a weird bug where concatenation is sometimes failing, and I
> have no idea why. See the attached pasm. I fully expect both works and
> weird to output "foo", "bar", "quux" with various levels of spacing,
> but weird doesn't output quux.
> ...
If I add just one print-command to that code,
# New Ticket Created by Leon Brocard
# Please include the string: [perl #16874]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt2/Ticket/Display.html?id=16874 >
Hi.
I have a weird bug where concatenation is sometimes failing, and I
have no idea wh
14 matches
Mail list logo
