scsh-hackers
[Top] [All Lists]

[Scsh-hackers] Re: More on file name grammar

To: shivers@cc.gatech.edu
Subject: [Scsh-hackers] Re: More on file name grammar
From: sperber@informatik.uni-tuebingen.de (Michael Sperber [Mr. Preprocessor])
Date: 20 Mar 2001 10:18:53 +0100
Cc: gasbichl@informatik.uni-tuebingen.de, scsh-hackers@lists.sourceforge.net, bdc@zurich.ai.mit.edu, alan@lcs.mit.edu
List-id: Discussion among the implementors <scsh-hackers.lists.sourceforge.net>
Sender: scsh-hackers-admin@lists.sourceforge.net
>>>>> "Olin" == shivers  <shivers@cc.gatech.edu> writes:

Olin> More on this issue of the root file/directory: it is a nasty little
Olin> bit of Unix that / is both a filename and a directory. The scheme
Olin> I presented in the previous msg represents the root *file* as empty
Olin> string, to which you append a slash (as you do with *all* files) to
Olin> get a directory, in this case "/".

This is all true as long as you're dealing with exclusively absolute
filenames.  The problem is, the filenames-as-strings API doesn't
distinguish them from relative ones, and you need to use the same damn
procedures to operate them. (That's the fundamental thing our filename
API does.)

-- 
Cheers =8-} Mike
Friede, Völkerverständigung und überhaupt blabla


<Prev in Thread] Current Thread [Next in Thread>
  • [Scsh-hackers] Re: More on file name grammar, Michael Sperber [Mr. Preprocessor] <=