Article View: borland.public.jbuilder.java.language
Article #20042JDK 1.1 Compiler differences
From: Lyle Thompson
Date: Wed, 05 Nov 1997 00:00
Date: Wed, 05 Nov 1997 00:00
34 lines
1540 bytes
1540 bytes
Hi all, We have found several differences between the errors generated by the JDK 1.1 compiler, and JBuilder's. It appears (from the limited sample) that JBuilder's compiler is somewhat better that Sun's. 1. There was a case where Sun's compiler did not notice an uncaught CloneNotSupportedException. 2. The JDK allows a method to be declared abstract synchronized. 3. A static blank final with a static initializer was erroneously flagged as uninitialized by JDK, but works with JBuilder. A try...catch was involved, because the constructor for the class of the field throws an exception. So far seems like an excellent compiler. Haven't tested these cases with Symantec though. One where JBuilder seems to fall short is in complaining that "variable may not have been initialized", when in fact all branches do, in fact, set the variable. Kudos and regards, Lyle -- Lyle Thompson Email: lyle@heliosoft.com HelioSoft, Inc. Phone: (510) 278-5249 664 Paseo Grande Fax: (510) 278-5249 San Lorenzo, CA 94580 Web: http://www.heliosoft.com
Technical Details
Message-ID:
<34615013.CF025F90@heliosoft.com>Path:
arc1-ca.pugleaf.net!unknown!not-for-mailShow Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: f74b3,47fae1d22c5dbac1,start X-Google-Attributes: gidf74b3,public From: Lyle Thompson <lylet@heliosoft.com> Subject: JDK 1.1 Compiler differences Date: 1997/11/05 Message-ID: <34615013.CF025F90@heliosoft.com> X-Deja-AN: 287339511 Reply-To: lyle@heliosoft.com Organization: HelioSoft, Inc. Newsgroups: borland.public.jbuilder.java.language