Dan --
> Here's something for someone looking to do something interesting while the
> code freeze is on.
>
> Write yourself a program that takes a .pasm file and, rather than spitting
> out bytecode, spits out the bodies of the opcode functions with the
> appropriate replacements done on the
In Configure.pl, one of the things I do is include Data::Dumper if it's
there, and skip the part that needs it otherwise. Unfortunately,
because of the compile-time nature of use, I can't do it. Thus, I have
to use the following hack:
my($DDOK)=eval {
require Data::Dumpe
Gregor N. Purdy:
# Dan --
#
# > Here's something for someone looking to do something
# interesting while the
# > code freeze is on.
# >
# > Write yourself a program that takes a .pasm file and,
# rather than spitting
# > out bytecode, spits out the bodies of the opcode functions with the
# > appro
All --
> My first cut is pretty sloppy, but it does generate this C file, which
> compiles, but I don't have the time to figure out how to get it all the
> stuff it needs to link to. If someones gets it running, I'd like to see
> how many Mops they get vs. regular.
BTW, I realized as I left the
Brent --
> # My first cut is pretty sloppy, but it does generate this C file, which
> # compiles, but I don't have the time to figure out how to get
> # it all the
> # stuff it needs to link to. If someones gets it running, I'd
>
> Parrot::Config may come in handy, especially @PConfig{qw(cc ccf
