Home   Info   DevZone   Wiki   UsersWeb  |  MainWeb  |  InfoWeb  |  DevZoneWeb  |  SupportWeb
[ JavaAPIFlaws ] [ not logged in ] [ Web: Imported ] goto:  options [ get info on or edit ] [ login or new user ] [ list of topics, hubs & nodes, or recent changes ]

Design flaws of the Java API

The Java APIs (java.*), defined by Sun, cover a large contingent of functions needed to write true cross-platform applications. However, some functions are underspecified; subtle, but nevertheless important details are left to the implementors. This can lead to compatibility problems.

This is why we want to document the way JOS implements java.* libraries in as great detail as possible. Eventually our efforts could help improve Sun's Java API specification in future releases.

Attention: This page is not for defining new APIs. It is for clarifying the meaning of individual methods etc. that are part of the standard Java APIs.

Package/Class/Method Problem How other VMs handle it Solution chosen for JOS java.io Are file/directory names CaseSensitive ? JDK leaves choice to the underlying OS, doesn't interfere still under discussion in jos-gui java.io.File.renameTo Can files be "renamed" (=moved) into another directory? In the JDK they can (at least under Windows), although this is not documented should behave alike java.lang.System System.in, System.out, System.exit etc. are designed for a one application/VM runtime JDK only runs one application per VM Rewrite that fields/method apply to current ExecutionContext only. See also ProcessGroup

Content of these pages are owned and copyrighted by the poster.
Hosted by: