Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!news.albasani.net!eternal-september.org!feeder.eternal-september.org!.POSTED!not-for-mail From: Gene Wirchenko Newsgroups: comp.lang.java.programmer Subject: Re: CLI Java Glitch Date: Tue, 21 Jun 2011 16:29:24 -0700 Organization: A noiseless patient Spider Lines: 23 Message-ID: References: <4dffe2ea$0$57121$c30e37c6@exi-reader.telstra.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Injection-Info: mx04.eternal-september.org; posting-host="7Qrvczazr82YckO5XW8Vtw"; logging-data="6981"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/HL9wegoDEuT0oYam/WjchWEA4q7KaoL4=" X-Newsreader: Forte Agent 4.2/32.1118 Cancel-Lock: sha1:JUCoAoBvEsy6cbqinYkI2YZ7/XU= Xref: x330-a1.tempe.blueboxinc.net comp.lang.java.programmer:5498 On Tue, 21 Jun 2011 22:49:59 +0100, Tom Anderson wrote: [snip] >The way Java does this at the moment means that 'java helloworld', where >there is no class 'helloworld', does different things on Windows depending >on whether there is a class HelloWorld, hElLoWoRlD, HelloworlD, etc. OP here. Not on my system. >That seems pretty shoddy to me. If you're a case-sensitive program running >on a case-insensitive operating system, i think it falls on you to pay >special attention to case in your dealings with that system: when java >opens a class file, it ought to check that the name of the file it's >opened actually has the right case, and if it doesn't, discard it, and act >as if it had got a file not found error from the operating system. But that is about what happened! Sincerely, Gene Wirchenko