Steve Fink <[EMAIL PROTECTED]> wrote: > Although this does bring up another issue -- should parrot really be > seg faulting when it gets a uninitialized (null) PMC?
The problem is of course that we call pmc->vtable->some_meth_od() on a NULL PMC. We could do the checks always, slowing down each PMC operation. But OTOH a correct HLL compiler wouldn't produce such broken code (hopefully). So that's probably something for the bounds-checking and safe run cores. Further if we have some kind of hint for the assembler, what is the main program, we could spit out an unitialized warning (the code is mostly there) and in case of an "in PMC" parameter make a fatal error out of it. leo
