From: jmoran
Subject: Problem with \ character on PC
Date: 
Message-ID: <35A55539.2EE7898C@tcd.ie>
Hi,
      I'm currently trying to get some code that worked on a mac working
on a PC. I'm having trouble with the reverse solidus character (ie #\\)
as it is used in pathnames on the PC. I can probably code around the
problem but there must be some standard way of dealing with this on PCs.
I'd appreciate any solutions.

Thanks,

John Moran

······@mail2.tcd.ie

From: David B. Lamkins
Subject: Re: Problem with \ character on PC
Date: 
Message-ID: <dlamkins-1007980920190001@192.168.0.1>
In article <·················@tcd.ie>, jmoran <······@tcd.ie> wrote:

>Hi,
>      I'm currently trying to get some code that worked on a mac working
>on a PC. I'm having trouble with the reverse solidus character (ie #\\)
>as it is used in pathnames on the PC. I can probably code around the
>problem but there must be some standard way of dealing with this on PCs.
>I'd appreciate any solutions.

Remember that \ is an escape character within a string.  So a DOS pathname
needs to be written like:

  "C:\\lisp\\foo.lsp"

The way to handle this portably (without #+ reader macros) is to use the
pathname functions instead of platform-dependent pathname strings.

-- 
David B. Lamkins <http://www.teleport.com/~dlamkins/>
From: Rainer Joswig
Subject: Re: Problem with \ character on PC
Date: 
Message-ID: <joswig-1107980103580001@194.163.195.67>
In article <·························@192.168.0.1>, ········@teleport.com
(David B. Lamkins) wrote:

> In article <·················@tcd.ie>, jmoran <······@tcd.ie> wrote:
> 
> >Hi,
> >      I'm currently trying to get some code that worked on a mac working
> >on a PC. I'm having trouble with the reverse solidus character (ie #\\)
> >as it is used in pathnames on the PC. I can probably code around the
> >problem but there must be some standard way of dealing with this on PCs.
> >I'd appreciate any solutions.
> 
> Remember that \ is an escape character within a string.  So a DOS pathname
> needs to be written like:
> 
>   "C:\\lisp\\foo.lsp"
> 
> The way to handle this portably (without #+ reader macros) is to use the
> pathname functions instead of platform-dependent pathname strings.

LWW allows you to use /, too.

Btw., nice XFACE.