Computer Chess Club Archives


Search

Terms

Messages

Subject: Re: crafty, epdpfga bug?

Author: Robert Hyatt

Date: 07:05:58 05/15/00

Go up one level in this thread


On May 14, 2000 at 22:34:17, Dave Gomboc wrote:

>On May 13, 2000 at 09:15:10, Robert Hyatt wrote:
>
>>On May 13, 2000 at 07:36:59, Dave Gomboc wrote:
>>
>>>tried to run
>>>
>>>epdpfga "c:\documents and settings\dave\my documents\epd.epd" "c:\documents and
>>>settings\dave\my documents\out.epd"
>>>
>>>but crafty v17.10 complained:
>>>
>>>This command takes two parameters
>>>EG fault: a problem occurred during epdpfga processing
>>>
>>>Presumably the difficulty is with the spaces in the path (why I quoted them --
>>>when I didn't, that gave an error too).  I tried to escape each space instead:
>>>
>>>epdpfga c:\documents\ and\ settings\dave\my\ documents\epd.epd c:\documents\
>>>and\ settings\dave\my\ documents\out.epd
>>>
>>>but that didn't work either.  Unfortunately, FAT32 doesn't support symbolic
>>>links, so this is kind of a pain.  In the DOS days I would have used subst to
>>>create a new drive letter pointing to c:\doc&set\dave\my_doc but I'm not sure if
>>>that's still around under NT.
>>>
>>>Dave
>>
>>
>>That comes from Steven's code.  I assume he doesn't handle spaces correctly,
>>since this was written before windows and the rather ridiculous concept of
>>spaces in a file name (yes, I know, you can put _any_ character in a filename
>>in unix, if you know how.  You can also put your hand in a blender...)
>
>Your old-timer prejudices are showing. ;-)  (By that, I mean that a path with a
>space in it, namely "c:\program files\...", exists on just about every windows
>9x/nt/2000 machine there is, and it only looks silly if you're not used to it!)
>
>Yeah, one of my attempts was to escape spaces with a \, a la some unix shells.
>No dice.  Ah well, I got around it with only minor bletcherousness.
>
>Dave


Spaces in filenames was a stupid idea.  I want to parse a list of filenames...
now I can't.  Because some filenames look like 2 filenames, since whitespace has
_always_ been a delimiter.  And windows doesn't quote the space in any way to
make it clear it is part of a single filename, rather than a delimiter for
two filenames...

ugh...



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.