Claudio Natoli wrote:
>>To the best of my knowledge, only the command processor cares about
>>this, and you can get around it by quoting the command - see
>>my initdb.c for examples. (this is also why I pass PGDATA via the
>>never via the command line - the Windows command processor is
>>quite dumb about multiple quoted strings). AFAIK direct library calls
>>like stat() or fopen() should accept forward slashes. It may be that
>>libraries other than MSVCRT act differently, although that would be very
>>even for M$.
>They will, as long as there isn't a mix of forward and backward slashes,
>which is currently the case in the backend code. Either canonicalize on
>forward, or #define out backslashes in Win32. In either case, it is an
>outstanding TODO item for postgres under win32.
Right. FWIW, I found canonicalization by far the simpler approach -
which I adopted after tying myself in knots doing things the other way.
In response to
pgsql-hackers-win32 by date
|Next:||From: Joshua D. Drake||Date: 2003-11-06 22:54:40|
|Subject: Committing Resources to Win32|
|Previous:||From: Claudio Natoli||Date: 2003-11-03 03:57:33|
|Subject: Re: Other Win32 TODO items?|