From: Phil S. <al...@ca...> - 2004-09-23 22:02:14
|
On Thu, Sep 23, 2004 at 03:22:10PM -0400, Michael K. Johnson wrote: > On Thu, Sep 23, 2004 at 12:22:28PM -0400, Phil Stracchino wrote: > > Of course, this is going to be a little difficult on Unix, because > > almost any character is legal in a Unix filename if escaped. I'm not > > sure I know of any character which MAY NOT, period, be used in a Unix > > filename. > > The only illegal filename character on Unix is the "/". Well, and > \0 -- which is implied because the C string is defined to end with > a \0 character, and the base ABI for dealing with these strings is > the C API. > > It has nothing to do with escaping any characters. The filesystem > doesn't have the concept of escaping a character. That's a shell > contruct only, which is only related to the filenames in that filenames > sometimes show up as arguments passed to programs, and that shells > tend to have filename globbing functions. > > (You probably knew that, but I figured I'd make sure to clarify > anyway. :-) Well, yeah. :) So, if one was to go that route, the string '/:\' would be an illegal filename on Mac, Windows, and Unix. (And VMS, I think....? My memories of VMS are hazy.) -- ========== Fight Back! It may not be just YOUR life at risk. ========== al...@ca... : phi...@ea... : ph...@no... phil stracchino : unix ronin : renaissance man : mystic zen biker geek 2000 CBR929RR, 1991 VFR750F3 (foully murdered), 1986 VF500F (sold) Linux Now! ...Friends don't let friends use Microsoft. |