Date: Tue, 25 Feb 1997 11:29:40 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To: Erik Max Francis <max AT alcyone DOT com>
cc: djgpp AT delorie DOT com
Subject: Re: Forgive my ignorance, but can someone answer a question for me?
In-Reply-To: <33128915.4B54D12E@alcyone.com>
Message-ID: <Pine.SUN.3.91.970225112548.6964B-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


On Mon, 24 Feb 1997, Erik Max Francis wrote:

> > about such filenames (the current code in libc collapses multiple
> > slashes into a single slash).
> 
> As do most Unix shells:
> 
>     max AT newton:~% ls Tmp
>     array       array.cc    array.o
>     max AT newton:~% ls Tmp//array.cc
>     Tmp//array.cc
         ^^
This tends to say the opposite: `ls' got the double slashes verbatim, but 
they didn't confuse it.  This is compatible with what I know: the slashes 
are collapsed inside Unix system calls, not by the shell.  Which is 
correct, I think: the shell has no business knowing which arguments are 
filenames and which aren't.  Otherwise it would collapse, e.g., Sed 
commands like s/foobar//.