Path: csiph.com!newsfeed.hal-mli.net!feeder3.hal-mli.net!newsfeed.hal-mli.net!feeder1.hal-mli.net!gegeweb.org!aioe.org!.POSTED!not-for-mail
From: glen herrmannsfeldt <gah@ugcs.caltech.edu>
Newsgroups: comp.lang.java.programmer
Subject: Re: Space in 'My Documents' directory not fixed by quoting or \ escaping
Date: Tue, 29 May 2012 21:43:38 +0000 (UTC)
Organization: Aioe.org NNTP Server
Lines: 25
Message-ID: <jq3fua$heb$1@speranza.aioe.org>
References: <jq2eme$o07$1@dont-email.me> <4fc4c1cb$0$6931$e4fe514c@news2.news.xs4all.nl> <a2jvh9FuhU1@mid.individual.net> <jq2l4h$2kl$2@news.albasani.net> <23u9s7tr13usskfhim78anlj5g8pe3q9l1@4ax.com> <899d499e-c1ad-4863-b941-575aaaac1c4b@googlegroups.com>
NNTP-Posting-Host: H0vc4U5LIRkRHNPyGCs2dA.user.speranza.aioe.org
X-Complaints-To: abuse@aioe.org
User-Agent: tin/1.9.6-20100522 ("Lochruan") (UNIX) (Linux/2.6.32-5-amd64 (x86_64))
X-Notice: Filtered by postfilter v. 0.8.2
Xref: csiph.com comp.lang.java.programmer:14915

Lew <lewbloch@gmail.com> wrote:

(snip)
>> But since using "/" as a path element seprator in a command line
>> will cause trouble, people tend to avoid using them as such.

> That is interesting to me. What trouble?

> I have used forward slashes as path element separators in Windows 
> command-line commands. I don't recall that it caused any trouble.

The system calls, such as OPEN, accept either / or \.
(C programmers use / for #include files, knowing it will work
on unix or DOS/Windows, at least since DOS 3.2.)

The system command line utilities, such as DIR and COPY use / for
options, and won't accept it as part of a file path.

Other command line utilities (that don't come with DOS/Windows)
that don't use / for options likely will accept /.

The Sourceforge UNXUTILS, unix-like utilities for WIN32, 
for example, should accept /.

-- glen