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 the
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:
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
On Tue, Sep 18, 2001 at 10:40:30PM +0100, Simon Cozens wrote:
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? :)
Sort of, while talking about other things. I wanted to drag it out to
On Tue, 18 Sep 2001, Damien Neil wrote:
Proposed: Parrot should never crash due to malformed bytecode. When
choosing between execution speed and bytecode safety, safety should
always win.
I don't see this as a safety issue. There's nothing unsafe about
crashing. It's just not as pretty as
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
At 02:37 PM 9/18/2001 -0700, Damien Neil 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 the speed
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 model
