Author: Robert Hyatt
Date: 14:09:32 07/06/02
Go up one level in this thread
On July 06, 2002 at 10:41:37, Daniel Clausen wrote: >On July 05, 2002 at 23:16:34, Robert Hyatt wrote: > >[snip] > >>It is impossible. There is a logpath variable you can set, but unfortunately, >>microsoft chose to make a brain-dead decision to allow spaces (blanks) in >>filenames. This breaks my parsing in crafty and I refuse to fix something that >>is so basically flawed... > >??? What is so bad about allowing blanks in filenames? I know an OS family which >allows any character except the slash and '\0' to be part of a filename and it's > a good thing. > >A confused Sargon In unix, you _can_ put any character you want in a filename. You also _can_ put your foot under a running lawnmower, or use a chainsaw to trim your hair. You _can_ do that. Whether you should or not is another subject, of course. But as to why it is bad, windows uses a "blank" to delimit commands and optional parameters. "xxx yyy zzz". If you put a blank in the path of the command name, you break things... Now you have to parse an overloaded operator. <space> might delimit the next field, or it _might_ just be a character in a filename. It is ok to _allow_ this as unix allows any character you want printable or not. It is _not_ ok to make it a standard directory in the system (program files) for the above reason...
This page took 0 seconds to execute
Last modified: Thu, 15 Apr 21 08:11:13 -0700
Current Computer Chess Club Forums at Talkchess. This site by Sean Mintz.