Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!weretis.net!feeder4.news.weretis.net!newsfeed.utanet.at!newscore.univie.ac.at!aconews-feed.univie.ac.at!aconews.univie.ac.at!not-for-mail Newsgroups: comp.lang.java.programmer From: Andreas Leitgeb Subject: Re: A strange behaviour of a File property References: <5980efbc-9010-4145-b886-fe106c5ac2d5@c18g2000yqj.googlegroups.com> <4ebef5e8$0$290$14726298@news.sunsite.dk> Reply-To: avl@logic.at User-Agent: slrn/pre0.9.9-111 (Linux) Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Message-ID: Date: 13 Nov 2011 01:28:13 GMT Lines: 27 NNTP-Posting-Host: gamma.logic.tuwien.ac.at X-Trace: 1321147693 tunews.univie.ac.at 60386 128.130.175.3 X-Complaints-To: abuse@tuwien.ac.at Xref: x330-a1.tempe.blueboxinc.net comp.lang.java.programmer:9893 Arne Vajhøj wrote: > On 11/12/2011 5:09 PM, Andreas Leitgeb wrote: >> Eric Sosman wrote: >>> On 11/11/2011 10:21 PM, Andreas Leitgeb wrote: >>>> Eric Sosman wrote: >>>>> [...] Note that in some file systems >>>>> there is no such thing as a "path separator;" on one such I had >>>>> files with names like >>>>> SYS$DISK:[USERS.ERIC.PROJECT]README.TXT;22 >>>> Such beasts still exist in the wild? >>> http://en.wikipedia.org/wiki/Files-11#Disk_organization_and_naming >>> "A fossil!" I hear you cry, "A dried relic of prehistory!" >> I'm not the type who would cry out about it, but I admit, I did think >> something more or less similar. > I do not consider version numbers prehistoric relics. Of course not those... (I think I've seen them even in some modern filesystems with versioning support). But I do consider the brackets enclosing the directory part of a file's path to be such. (namely prehistoric relics) > * Java actually supports both native syntax and traditional > *nix / syntax for filenames So that gets us back to the start: Just using "/" as dir-separator is very likely to get you far enough.