Re: How to set a breakpoint in file, which name has spaces?

[Mark Kettenis <mark.kettenis@xs4all.nl>]

> Date: Sat, 12 Aug 2006 17:20:20 +0300
> From: Eli Zaretskii <eliz@gnu.org>
> 
> > Date: Sat, 12 Aug 2006 13:44:05 +0200 (CEST)
> > From: Mark Kettenis <mark.kettenis@xs4all.nl>
> > CC: Nikolay.Molchanov@Sun.COM, gdb@sourceware.org
> > 
> > > Date: Fri, 11 Aug 2006 15:55:40 +0300
> > > From: Eli Zaretskii <eliz@gnu.org>
> > > 
> > > > Date: Thu, 10 Aug 2006 22:26:55 -0700
> > > > From: Nikolay Molchanov <Nikolay.Molchanov@Sun.COM>
> > > > Cc: gdb@sourceware.org
> > > > 
> > > > I hope we will never need to set a breakpoint in a file,
> > > > which name has double quotes :-)
> > > 
> > > MS-Windows filesystems don't allow file names with double quotes, so
> > > you needn't worry about that.
> > 
> > But POSIX systems do allow it:

Correctling myself, POSIX (EEE Std 1003.1-2001) itself doesn't allow
allow double quotes.

> 
> Do they also have drive letters?  The original discussion was about
> file names such as C:/Documents and Settings/foo.c.

Sigh, the Microsoft employee who came up with the bright idea to put
spaces in standard directory names must have been a complete moron.

Anyway, no they don't have drive names, but C: is a valid filename on
OpenBSD, as are spaces.  So on OpenBSD your example is also a possible
file name.  Of course nobody in their right mind would actually create
such a name on an OpenBSD system.

> In other words, this whole thread was about Windows file names with
> spaces in them.  So POSIX file-name (un)restrictions are not really
> relevant.

Well, I might have missed something, but the discussion also was about
quoting file names in commands, and I really hope you're not
suggesting that we should have seperate quoting rules for Windows and
POSIX-like systems.

Mark