Re: Modifications to sanity.sh to support MSVC binary

[Spiro Trikaliotis]

Hello,

* On Wed, Jun 21, 2006 at 09:54:55AM -0400 Jim Hyslop wrote:
 
> One of the biggest stumbling blocks to getting the MSVC binary to work
> with sanity.sh is the path convention (i.e. / vs. \).

I am not familiar with the CVS sources (or sanity.sh), but is this
really necessary? Every Win32 API call can handle BOTH path specifiers,
even in mixed form! That is, c:\abc\def\gh and c:/abc/def/gh and
c:\abc/def\gh are all valid file names, and they point to the same file!
This works even for UNC names: \\server\abc and //server/abc are both
valid.

This was true even in the old DOS days: I checked myself with MS-DOS
3.3, it accepted both forms.

It is only many user-level tools (like cmd.exe and command.com) which
have problems with the slash as path separator.

Or do I misunderstand the problem at hand?

Regards,
   Spiro.

-- 
Spiro R. Trikaliotis                              http://opencbm.sf.net/
http://www.trikaliotis.net/                     http://www.viceteam.org/