Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!goblin3!goblin.stu.neva.ru!exi-transit.telstra.net!news.telstra.net!exi-spool.telstra.net!exi-reader.telstra.net!not-for-mail Date: Tue, 21 Jun 2011 10:16:40 +1000 From: Esmond Pitt Reply-To: not.esmond.pitt@not.bigpond.com User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-GB; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10 MIME-Version: 1.0 Newsgroups: comp.lang.java.programmer Subject: Re: CLI Java Glitch References: In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Lines: 12 Message-ID: <4dffe2ea$0$57121$c30e37c6@exi-reader.telstra.net> NNTP-Posting-Host: 120.151.14.51 X-Trace: 1308615402 exi-reader.telstra.net 57121 120.151.14.51:35359 Xref: x330-a1.tempe.blueboxinc.net comp.lang.java.programmer:5448 On 21/06/2011 8:09 AM, Martin Gregorie wrote: > > The Java language system does case-sensitive comparisons between class > names and the files that contain them when checking that a class name > matches the file name that contains it Nitpicking, but it doesn't really do that, does it. It opens a .class file of the name the user specified, loads the class(es) it contains, and tries to find the classname it was looking for among those classes. It doesn't explicitly compare the filename and the classname. The operating system gave it HelloWorld.class in response to 'helloworld.class' because that's how the OS file system happened to work.