Jaen Saul:
> Since you are making a release pretty soon, I'm reporting the state of
> Parrot on Win32 and running my tinderbox client :)
Don't worry, Parrot won't fly without you!
> Tests: fail. miserably. 100% crashed :) probably some illegal pointer deref.
Can you try it now? This won't fix a
Hi,
Since you are making a release pretty soon, I'm reporting the state of
Parrot on Win32 and running my tinderbox client :)
Parrot compiles nicely, but compiling it requires quite much memory,
sometimes the compiler process takes up more than 32MB...
The reason of course is the gigantic core_op
At 11:07 PM -0500 3/5/02, Bryan C. Warnock wrote:
>
>Three quick things:
>1) INTVALs and opcode_t > longs will now be even more suspect than what
>they were beforehand.
>2) Feel free to bicker with names. I don't think we've come to *any* sort
>of agreement with these, although we really, really
I'll apply these both later on today--I want to finish some abuse of
the memory allocation system first.
--
Dan
--"it's like this"---
Dan Sugalski even samurai
[EMAIL PROTECTED]
> What's the warning here? Code looks fine to me, and the organization is
> more logical if it's up top.
Since BOOLVAL is a char, padding for alignment. (Of course, gcc (3.0.4)
still warns at the end.)
'Tain't important.
>
> --Brent Dax <[EMAIL PROTECTED]>
> @roles=map {"Parrot $_"} qw(embed
Bryan C. Warnock:
# Some minor annoyances.
#
# Index: include/parrot/rx.h
# ===
# RCS file: /home/perlcvs/parrot/include/parrot/rx.h,v
# retrieving revision 1.16
# diff -u -r1.16 rx.h
# --- include/parrot/rx.h 4 Mar 2002 03:38:23 -000
