DOS/Windows and slashes (was Re: Windows XP Pro and Possible filePro Bug)

[Bob Stockler]

On Sat, Dec 04, 2004 at 11:52:46AM -0500, Ken Brody wrote:
| Bob Stockler wrote:
| [...]
| > | Just a thought as I am not running sp2 here. Have you tried using windows back
| > | slash rather then the *nix right slash?
| > |
| > | This might be a problem with fp translating the slashes.
| > 
| > I am _positive_ that filePro is _not_ confused by one using
| > forward slashes on Windows filePro User Menu command lines.
| > 
| > I am fairly certain that filePro translates the / or \ in
| > pathnames in all it's stuff to be the one appropriate for
| > the OS.
| [...]
| 
| DOS and Windows have always allowed both "/" and "\" as path separators.
| (Well, "always" as in "as long as DOS has supported paths in DOS 2.0".)
| It is command.com and some applications that do not allow "/" in paths,
| but the kernel itself has always allowed both.
| 
| There is reason, for example, to do this:
        ^^^^^^^^^
I think you meant "NO reason".

Bob

|     If:  @OS = "DOS"
|   Then:  zz = chr("92")
|     If:  @OS ne "DOS"
|   Then:  zz = "/"
|     If:
|   Then:  fn = zz & "path" & zz & "to" & "filename.txt"
|     If:
|   Then:  export ascii out=(fn) f=, r=\n
| 
| when this works on all platforms:
| 
|   Then:  export ascii out="/path/to/filename.txt" f=, r=\n
| 
| -- 
| +-------------------------+--------------------+-----------------------------+
| | Kenneth J. Brody        | www.hvcomputer.com |                             |
| | kenbrody/at\spamcop.net | www.fptech.com     | #include <std_disclaimer.h> |
| +-------------------------+--------------------+-----------------------------+
| Don't e-mail me at: <mailto:ThisIsASpamTrap at gmail.com>

-- 
Bob Stockler - bob at trebor.iglou.com
Author: MENU EDIT II - The BEST Creator/Editor/Manager for filePro User Menus.
Fully functional (time-limited) demos available by email request (specify OS).