If memory serves me right, Dan Sugalski wrote: > Sure. Or at least not forbidden.
k ... > that case, why bother verifying? Hmm.... wouldn't the JIT benifit from a pre knowledge of basic blocks and types or some information ? ... (I seem to think so ...). > at runtime anyway. With a full scan of the bytecode, of course, and > you'd need to figure where each and every instruction starts, which > can be costly. Can't that be added onto the JIT'ing process ? ... viz during conversion ,check for jump targets ?.. I still have this assumption that JITs need to maintain some sort of basic block identification for peephole optimisations ?.. Or is that totally irrelvant for register VMs ? ... (this is the first register VM I have encountered...) > >option (for the sake of speed freaks ?) parrot -fverify hello.pbc ? > > No, the option'd be more that you enable verification rather than > disable it. Speed is the default. Yup I meant just that .... not "-noverify' , but "-verify" :-)... So, Parrot is more secure than perl is ? (that being your benchmark). Gopal -- The difference between insanity and genius is measured by success
