[Bf-committers] Re: Blender command line args

GSR gsr.b3d at infernal-iceberg.com
Thu Mar 23 18:42:00 CET 2006


Hi,
cwant at ualberta.ca (2006-03-20 at 2044.46 -0700):
> Stephen Swaney wrote:
>  > <rant>
>  > Spaces in filenames used to be unthinkable before those *bleeps*
>  > in Redmond started doing it.  After that, scripting became a new
>  > sort of hell.
>  > </rant>
> Not quite -- recall that MS filenames were still restricted
> to 8.3 characters until 1995. Mac's, on the otherhand, commonly
> used spaces in filenames for ages before that (and I'm sure
> somebody will tell me that NeXT used spaces in filenames for
> ages before Mac's).

I have not exact dates, but Unix before that probably. And not only
spaces, any byte is valid in an Unix file or directory, except \0 and
'/' (and special meaning like single dot and double dot for dir
links... but those just are automatic links, not invalid).

Never had a file named "-r" or "*"? Anybody doing scripting has found
those (probably after creating them by error). And also has wondered
about the different styles for parameters or why some comands default
to stdin/stdout and others are just unable to do it without extra
steps. Or why your regexp is not the same in different apps... bah, if
you want rants, you are late. ;]

GSR
 


More information about the Bf-committers mailing list