Gregor N. Purdy <[EMAIL PROTECTED]> wrote:
> ..., but I didn't want to make
> 2 * N new .c files to get paranoid versions of the N core .c
> files now.
One safe core, built separately with its own Ops files ought to be
enough, IMHO.
> I thought about prederef a bit right before submitting this,
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 exec
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. T
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 whet
Okay, it's time to start in, at least a little, on safe mode for parrot.
While there's a *lot* to ultimately do, the initial part, a paranoid set
of ops and a runloop that understands it, is relatively simple. What we
need is someone to thump the code that generates the core_ops.c files (and
their
