Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!gegeweb.org!de-l.enfer-du-nord.net!feeder1.enfer-du-nord.net!cs.uu.nl!news.stack.nl!.POSTED!ipv6.urchin.earth.li!twic From: Tom Anderson Newsgroups: comp.lang.java.programmer Subject: Re: CLI Java Glitch Date: Tue, 21 Jun 2011 22:52:00 +0100 Organization: Stack Usenet News Service Lines: 45 Message-ID: References: NNTP-Posting-Host: ipv6.urchin.earth.li Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Trace: mud.stack.nl 1308693120 53117 2001:ba8:0:1b4::6 (21 Jun 2011 21:52:00 GMT) X-Complaints-To: abuse@stack.nl NNTP-Posting-Date: Tue, 21 Jun 2011 21:52:00 +0000 (UTC) User-Agent: Alpine 2.00 (DEB 1167 2008-08-23) In-Reply-To: Xref: x330-a1.tempe.blueboxinc.net comp.lang.java.programmer:5492 On Mon, 20 Jun 2011, Martin Gregorie wrote: > On Mon, 20 Jun 2011 14:24:53 -0700, Gene Wirchenko wrote: > >> Dear Java'ers: >> >> Given >> >> class HelloWorld >> { >> public static void main(String[] args) >> { >> System.out.println("Hello, world!"); >> } >> } >> >> is there any way around the following? >> > Nope: out it down to the non-intuitive ways some OSen handle file names. > There's a big difference between: > > (1) an OS that stores a file name as input but does caseless name > comparisons when parsing a request to find a file (Windows from Win95 > onwards) > > and > > (2) one that converts file names to, say, upper case when they're stored > and *then* does caseless comparisons. (DOS, Windows to 3.11) > > or > > (3) one that stores file names as entered and does case-sensitive > comparisons. (all UNIX family OSen) Ahem. The UNIX-family MacOS X - possibly only when using HFS+ and FAT, although i'm not sure - does case-wobbly comparisons. Case is preserved, but i think it is ignored when paths are looked up. It's been a while since i worked on OS X, so i forget the details. tom -- No man ever steps in the same river twice, for it's not the same river and he's not the same man. -- Heraclitus