Cliff Crick wrote:
> Roly Perera wrote:
> > >
> > > Sun's certainly gone to some length to make sure
StackOverflowError
> > > appears to be thrown at some particular point. InternalErrors are
> > > never thrown because we don't have recoverable errors; i.e. the VM
> > > crashes instead. :-)
> >
> > The JLS (in 11.3.1 and 11.3.2) requires precision for all Errors,
even
> > InternalError, which is the only asynchronous Error which can be
> > thrown by the VM. (A side issue is that there is *no* apparent
> > circumstance under which UnknownError can be thrown, unless it is
> > perhaps intended to be a synchronous form of InternalError.)
>
>
> Right, StackOverflowError is thrown precisely. InternalError isn't
> thrown (but see next email on MappedByteBuffers) from normal
> Java code. Not sure if this has anything to do with JMM.
I suspect even specifying that InternalError is precise is fairly
meaningless, since it never occurs in a correct implementation. (I.e.
if strange event orderings are observed in the presence of an
asynchronous InternalError, so what?)
Roly
> Cliff
>
>
> --
> Cliff Click Compiler Designer and Researcher
> cliffc at acm.org Java Software
> (408) 863-3266 MS UCUP02-302
-------------------------------
JavaMemoryModel mailing list - http://www.cs.umd.edu/~pugh/java/memoryModel
This archive was generated by hypermail 2b29 : Thu Oct 13 2005 - 07:00:34 EDT