Re: OODL: Java VM and bytecodes as models

[M. Uli Kusterer]

>> gcc bytecode is nice for compilers, but I doubt it's appropriate for
>>OpenCard. You wouldn't want to have to compile your stack every time you
>>change a script.
>
>Well, with the current Interpreter you do have to compile the relevant
>script every time you change it, and you do want to do that. It's a lot
>faster.

Anthony,

 I am aware of that (Velocity worked the same way, as you might remember,
just a lot slower), but what I was referring to was that gcc bytecode is
intended to be compiled again, not to be executed. Thus I thought it might
be a lot slower to run than your Interpreter's intermediate code.

 BTW -- did you check out the new XBlockFile? I'm still waiting for someone
to find my mistakes ???

Cheers,
-- M. Uli Kusterer

------------------------------------------------------------
             http://www.weblayout.com/witness
       'The Witnesses of TeachText are everywhere...'

--- HELP SAVE HYPERCARD: ---
Details at: http://www.hyperactivesw.com/SaveHC.html
Sign: http://www.giguere.uqam.ca/petition/hcpetition.html