On Wed, 2009-08-26 at 12:52 -0700, John R Pierce wrote:
> Sam Mason wrote:
> > On Wed, Aug 26, 2009 at 02:55:37PM +0000, Ken Smith wrote:
> >
> >> I also noted
> >> that if I try to run from the commandline that you use '/' in some of the
> >> program paths causing the OS to say it cannot find the file - "C:/Program
> >> Files/Java/jdk1.5.0_16/jre/bin/java.exe".
> >>
> >
> > I'm pretty sure that Windows has known about forward slashes being path
> > delimiters since Windows 95 and the start of Win32. I know I normally
> > use forward slashes in XP when I'm at work!
> >
>
>
> they work in the APIs but not in the CMD command line shell, as it
> expects / to be the command option seperrator (much as - is used in
> Unix-like systems)
That's very program specific - it's part of the program's command line
parsing and argument processing, not cmd.exe / CreateProcess(...)'s
handling of the command line arguments.
Most Windows utilities, including command-line tools, handle
forward-slash paths quite fine. It's just a few nasty old DOS-like ones
that're a problem ... but that does include many of the basic cmd.exe
built-in commands :-(
--
Craig Ringer
