Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!weretis.net!feeder4.news.weretis.net!usenet.ukfsn.org!not-for-mail From: Martin Gregorie Newsgroups: comp.lang.java.programmer Subject: Re: A strange behaviour of a File property Date: Sun, 13 Nov 2011 12:42:27 +0000 (UTC) Organization: UK Free Software Network Lines: 48 Message-ID: References: <5980efbc-9010-4145-b886-fe106c5ac2d5@c18g2000yqj.googlegroups.com> <4ebef5e8$0$290$14726298@news.sunsite.dk> <4ebf2081$0$289$14726298@news.sunsite.dk> NNTP-Posting-Host: 84.45.235.129 Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Trace: localhost.localdomain 1321188147 30280 84.45.235.129 (13 Nov 2011 12:42:27 GMT) X-Complaints-To: usenet@localhost.localdomain NNTP-Posting-Date: Sun, 13 Nov 2011 12:42:27 +0000 (UTC) User-Agent: Pan/0.135 (Tomorrow I'll Wake Up and Scald Myself with Tea; GIT 30dc37b master) Xref: x330-a1.tempe.blueboxinc.net comp.lang.java.programmer:9902 On Sat, 12 Nov 2011 20:42:21 -0500, Arne Vajhøj wrote: > On 11/12/2011 8:28 PM, Andreas Leitgeb wrote: >> 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) > > So / is modern but [] is oldfashioned. > > Are there any objective reason for that? > >>> * 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. > > It will get you to where a user actually specify a filename in normal > native syntax. > ... but its best to get into the habit of assembling a filename along the lines of dirNameList + File.separator + fileName rather than using dirNameList + "/" + fileName -- martin@ | Martin Gregorie gregorie. | Essex, UK org |