> Date: Fri, 16 Jul 1999 10:49:47 -0500
> From: Jim Kimball <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
>
> It was my understanding that code wrapped in an exception handler
> introduces more overhead to the JVM. I am sure I have seen articles on
> this exact topic in Java World or Java Report.
sunwjit, symcjit and even hotspot do "implicit exceptions." Meaning a
null pointer exception is detected from a SIGSEGV, and the VM raises
the related NullPointerExcetion from the signal handler. This offers
the best performance for the normal case where there isn't a NPE. In
general, doing co
> Date: Sun, 27 Jun 1999 21:17:37 -0700
> From: Nathan Meyers <[EMAIL PROTECTED]>
>
> > > How many of their patches have gone back into the Java tree?
> >
> > Many of them are going into 1.3.
>
> People are talking about 1.3? Not 1.2.3?
Yes, 1.3.
If you were at JavaOne, the Java 2 SE roadmap
> Date: Sat, 5 Jun 1999 15:29:50 -0700 (PDT)
> From: Bob Cadenza <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
>
> First off, using jdk117v3 I have the enviorment
> setting CLASSPATH='./' so I can test trusted applets. But now using
> the jdk1.2v2 the applets are no lo
In 1.2 symbols are found in a libraries associated with your class's
ClassLoader. Meaning: if Foo.bar was a native method then the symbol
Java_Foo_bar is searched in the set of libraries loaded by Foo's
ClassLoader. This was a bug fix that makes resilient field and method
ID caching in the pres
[EMAIL PROTECTED] (Joseph H. Buehler) writes:
> [EMAIL PROTECTED] (Anand Palaniswamy) writes:
>
> > Another bad side effect of this limitation is that the famous "return
> > memory to OS" bug can not be implemented on Linux (ie, there is no
> > heap "sh
Peter Schuller <[EMAIL PROTECTED]> writes:
> > The reason for this is that the default -Xmx value is 64MB.
>
> But that's the *maximum* heap size; why does JDK 2.0 consume, in one
> particular case, 50 megs of RAM when JDK 1.1 consumed 15 megs, just
> because the *maximum* heap size is higher?
The reason for this is that the default -Xmx value is 64MB. On Linux
you can not treat
(1) reserving part your addresss space and
(2) comitting swap to it
as two different ops. You get both at one shot. (This is my
understanding, I could be wrong, please correct me if you are better
inform
"JDK 1.2" and "Java 2" are synonyms. Notice the missing decimal point
in the latter (atleast for now). I believe the release is _not_ JDK 2
or JDK 2.0 or Java 2.0. Please don't flame me about the confusion, me
just an engineer -- it was a marketing thang.
-Anand.
Gerald Gutierrez <[EMAIL PROTECTED]> writes:
> I'm starting to pull out my hair from the fact that the current JDK is
> based on user threads. I can't call anything that can potentially block,
> because everything will block.
"Green threads" converts all your blocking I/O into non-blocking ones
10 matches
Mail list logo
