From mboxrd@z Thu Jan  1 00:00:00 1970
Message-Id: <E87A0939-AA5A-4D98-BB8F-871A59CF8F10@orthanc.ca>
From: Lyndon Nerenberg <lyndon@orthanc.ca>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
In-Reply-To: <20080104022953.CE1461E8C1F@holo.morphisms.net>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v915)
Subject: Re: [9fans] frogs and osx
Date: Fri,  4 Jan 2008 00:24:48 -0700
References: <20080104022953.CE1461E8C1F@holo.morphisms.net>
Topicbox-Message-UUID: 26f30fa0-ead3-11e9-9d60-3106f5b1d025


On 2008-Jan-3, at 19:29 , Russ Cox wrote:

> In addition to NUL, surely / should be illegal!
> I certainly wouldn't want \n in file names; \r seems just too close.

Pathological egregiousness?

There is only one true separator, and that is '/'. In the context of  
pathnames, '/' is NUL as per C strings. NUL in pathnames is silly, but  
allowed, as per pathnames.

It makes no sense, but if you can push a NUL into a pathname, you  
should deal with the result. It's a pity the intermediate code has to  
do so as well ...