The verifier is part of the the class loading process, it's the first step of linking a class to the runtime. More about that can be found in [1], but the verifier makes sure that a given piece of bytecode won't mess up the stack or incorrectly use types.
Rodrigo [1] The Java Virtual Machine Specification, Second Edition On 5/11/05, FaeLLe <[EMAIL PROTECTED]> wrote: > So byte code verification can occur at runtime and still be a confronting > implementation ? > > I think it would make since as long as it occurs because even J2ME pre > verifies (as i guess you guys know) and that is accepted at run time as long > as it remains in that state. > > > On 5/11/05, Ben Laurie <[EMAIL PROTECTED]> wrote: > > > > Anthony Green wrote: > > > On Wed, 2005-05-11 at 10:42 +0100, Ben Laurie wrote: > > > > > >>I'm more interested in the modularity with this question - by the sound > > >>of it, the verifier is an optional module. > > > > > > > > > No, a conforming implementation requires a bytecode verifier. > > > > I thought we'd established that it didn't? That is, verification must > > occur, but it can occur at runtime. > > > > -- > > http://www.apache-ssl.org/ben.html http://www.thebunker.net/ > > > > "There is no limit to what a man can do or how far he can go if he > > doesn't mind who gets the credit." - Robert Woodruff > > > > -- > www.FaeLLe.com <http://www.FaeLLe.com> > >
