Dan --
Here's a first version that works with the regular core.
You have to explicitly define PARANOID, or the added code
won't get compiled.
I imagine this will have to be adapted to work with the other
core types, but I wanted to throw this out as a starting point.
I'll leave it up to you
Gregor N. Purdy [EMAIL PROTECTED] wrote:
Dan --
Here's a first version that works with the regular core.
You have to explicitly define PARANOID, or the added code
won't get compiled.
It IMHO should be a separate run core, which can be switched to,
whenever safe execution is desired. Then
Leo --
Thanks for taking the time to review and comment.
Here's a first version that works with the regular core.
You have to explicitly define PARANOID, or the added code
won't get compiled.
It IMHO should be a separate run core, which can be switched to,
whenever safe execution is
Robert Spier [EMAIL PROTECTED] wrote:
Anyway, we're more than happy to do this once in a while.. We just
require detailed instructions as to what goes where.
As Dan now seems to agree, that imcc (and other files) should go into
its own subdirectory it would be fine, it we could the move be
I just put together an entry on predereferencing in the glossary,
with pointers to info on various events in its history.
I don't remember if it was a recent summary or what, but someone
pointed out there was no such entry. Sorry I can't find the
original email to notify you directly, but I hope
The pasm files in examples/benchmarks give an error when run with
parrot, because they lack a final line feed character (at the very end
of the files):
error:imcc:parse error, unexpected EOM, expecting '\n'
in file 'examples/benchmarks/gc_waves_sizeable_data.pasm' line 85
I'd imagine this
