Yes this is true except when the identifier is the name
for a inner class definition. An inner class ends up on the local
file systems with a name like "outerclassname$innerclassname.class".
Cheers
Chris
Paolo Ciccone wrote:
> > "AG" == Aaron Gaudio <[EMAIL PROTECTED]> writes:
>
> AG>
On Fri, 22 Jan 1999 12:15:29 -0500 (EST), Aaron Gaudio wrote:
>It was my understanding that Java source code is only guaranteed to work if
>it's ASCII, but I may be wrong about that. Obviously, though, ASCII
The JLS specifies that source code is either in ISO-Latin-1 or UNICODE.
(ISO-Latin-1 is
> "AG" == Aaron Gaudio <[EMAIL PROTECTED]> writes:
AG> It was my understanding that Java source code is only
AG> guaranteed to work if it's ASCII, but I may be wrong about
AG> that.
No, you're right but the example give *is* ASCII. The spec refers to
the encoding of the source, n
> "AP" == Alex Pozgaj <[EMAIL PROTECTED]> writes:
AP> I just tried it out on Solaris (SunOS 5.6), both with jdk1.2
AP> and with jdk1.1.5.
AP> Under 1.2 it worked. Under 1.1.5, I got the same error message
AP> as you did.
AP> Oh, and something more: why in a wolrd would s
It was my understanding that Java source code is only guaranteed to work if
it's ASCII, but I may be wrong about that. Obviously, though, ASCII
seems the safe way to go. JDK 1.2 may have changed the internationalization
standards (officially or unofficially). Note that there could also be
a limita
