> > Splitting apart or putting together either one of these paths is trivial > > I think it's far from trivial, especially if you want to take into > account network names, file versions, protection attributes and ACLs, ... Access details like this are largely independent of the logical manipulations made with pathnames. I can claim that there is "/foo/bar/zap.txt" and I can say that file directory part is "/foo/bar", but whether such an entity really exists, is a different matter. > -- Johan -- $jhi++; # http://www.iki.fi/jhi/ # There is this special biologist word we use for 'stable'. # It is 'dead'. -- Jack Cohen
- Re: Internal Filename Representations (was Re: ... Nathan Wiger
- Re: Internal Filename Representations (was ... Chaim Frenkel
- Re: Internal Filename Representations (was Re: ... Dan Sugalski
- Re: Internal Filename Representations (was ... Jarkko Hietaniemi
- Re: Internal Filename Representations (... Chaim Frenkel
- Re: Internal Filename Representations (... Jarkko Hietaniemi
- Re: Internal Filename Representations (... Nathan Wiger
- Re: Internal Filename Representations (... Chaim Frenkel
- Re: Internal Filename Representations (... David L. Nicol
- Re: Internal Filename Representations (... Chaim Frenkel
- Re: Internal Filename Representations (was Re: Summary o... Jarkko Hietaniemi
- Re: Internal Filename Representations (was Re: Summ... Johan Vromans
- Re: Internal Filename Representations (was Re: ... Chaim Frenkel
- Re: Internal Filename Representations (was ... Bryan C . Warnock
- Re: Internal Filename Representations (... Jarkko Hietaniemi
- Re: Internal Filename Representations (... Chaim Frenkel
- Re: Internal Filename Representations (... Jarkko Hietaniemi
- Re: Internal Filename Representations (... Chaim Frenkel
- Re: Internal Filename Representations (... Jarkko Hietaniemi
- Re: Internal Filename Representations (... Kai Henningsen
- Re: Internal Filename Representations (... Jarkko Hietaniemi