Therefore the decision was taken that we should not guarantee that Parrot
should never segfault when fed bad assembler;
... in the "fast run case", but we will provide a save environment, that does do all kinds of bounds checking, check byte code, have a reduced and configurable opcode set (a la Safe.pm"), and that doesn't joke on "parrot -- - </dev/urandom", later ;-)
Simon
leo
