javadoc's current filenaming conventions are defective in several ways, such as:

1) names longer than 31 characters in length must be "mangled" on some
   platforms -- particularly the Macintosh.

2) names containing multiple periods are problematic for some operating systems
   (e.g., OpenVMS) -- see the Comments for details.

3) writing to CDs, where the limitation is 64 characters.

-- Mark Scott Johnson (on behalf of Doug Kramer)



Name: gsC80088 Date: 02/18/99


In many cases filenames used in JDKs and some of the documentation are too long for the systems on the receiving end, so to speak. I have a Macintosh and am trying to learn Java from your web site. Your docs are excellent -- its great to see it all on-line. However, its very fustrating that many of theme of the filenames are too long for MacGzip (GNU gzip for the Macintosh) -- it can't create files whose names are too long, so it just skips 'em... This occurs in several compressed archives: JDK 1.2 and some of your tutorials, etc. I know these namesare readable, but surely they can be kept to 30 characters or less?
This is a pity in particular as the main point of Java is to be machine-independent, but your docs, class libraries, examples, etc., aren't quite machine-independent...!
Could you ***please*** fix this??? Metrowerks must have had to patch this up too, when I think about it -- it must be a nuisance to them, too.
======================================================================