At 06:44 PM 9/18/2001 -0700, Hong Zhang wrote:
> > Proposed: Parrot should never crash due to malformed bytecode. When
> > choosing between execution speed and bytecode safety, safety should
> > always win. Careful op design and possibly a validation pass before
> > execution will hopefully keep
> Proposed: Parrot should never crash due to malformed bytecode. When
> choosing between execution speed and bytecode safety, safety should
> always win. Careful op design and possibly a validation pass before
> execution will hopefully keep the speed penalty to a minimum.
We can use similar mo
Gibbs Tanton <- tgibbs <[EMAIL PROTECTED]>> writes:
> I would vote no. HOWEVER, I would think that the user should have the
> option to turn on checking for malformed bytecode (i.e. Safe mode). In
> the default case, I think the bytecode should be assumed well formed and
> no extra checking be
On Tue, Sep 18, 2001 at 02:37:43PM -0700, Damien Neil wrote:
> Proposed: Parrot should never crash due to malformed bytecode.
Haven't we done this argument? :)
I'd vote no, FWIW.
--
Dames lie about anything - just for practice. -Raymond Chandler
I would vote no. HOWEVER, I would think that the user should have the
option to turn on checking for malformed bytecode (i.e. Safe mode). In the
default case, I think the bytecode should be assumed well formed and no
extra checking be performed.
-Original Message-
From: Damien Neil
To:
