At 4:22 PM -0500 2/17/02, Melvin Smith wrote:
>You were correct, I'm not sure why you thought pbc2c was the
>default method of running parrot files. I thin pbc2c is just a proof
>of concept toy.
pbc2c is a bit more than a proof of concept, though it'll be a bit
before it's past the toy implement
>-Melvin
>-Melvin
Sorry, I got stuck in a for loop. :)
On Sun, Feb 17, 2002 at 08:54:52PM +0100, Gerson Kurz wrote:
> Besides, wasn't parrot supposed to be a VM and interpret the code,
> rather than just compile-to-c? (And, the code doesn't even look like
> normal C code - it has a "static char program_code[] = {" which it
> executes).
Yes. You're us
At 09:38 PM 2/17/2002 +0100, Gerson Kurz wrote:
>~/parrot>assemble.pl examples/assembly/euclid.pasm >test.pbc
>~/parrot>pbc2c.pl test.pbc >test.c
>Use of uninitialized value in sprintf at lib/Parrot/OpTrans/CGoto.pm line
>97.
>~/parrot>
Just run the bytecode with the interpreter instead.
../test
On Sun, 17 Feb 2002, Gerson Kurz wrote:
> Hi Brent,
>
> you wrote:
> > Did you follow the directions in the README file? That assemble.pl
> > warning especially makes me very suspicious.
>
> I'm sorry, I got it wrong in the mail. I did the configure/make/make test
> thing. This is what happened:
Hi Brent,
you wrote:
> Did you follow the directions in the README file? That assemble.pl
> warning especially makes me very suspicious.
I'm sorry, I got it wrong in the mail. I did the configure/make/make test
thing. This is what happened:
~/parrot>assemble.pl examples/assembly/euclid.pasm >t
Gerson Kurz:
# I downloaded
#
# http://cvs.perl.org/snapshots/parrot/parrot_2002-02-17_14.tar.gz
#
# to try fooling around with parrot on cygwin.
#
# 1) Some files are missing, so make.pl fails. Luckily for me I'm not an
# alpha-or-sun-user (missing: jit/sun4/lib.jit and string.jit - they are
