Date:	Mon, 01 Oct 2001 13:48:48 +0200
From:	"Eli Zaretskii" <eliz AT is DOT elta DOT co DOT il>
Sender:	halo1 AT zahav DOT net DOT il
To:	Tim Van Holder <tim DOT van DOT holder AT pandora DOT be>
Message-Id:	<1438-Mon01Oct2001134848+0300-eliz@is.elta.co.il>
X-Mailer:	Emacs 20.6 (via feedmail 8.3.emacs20_6 I) and Blat ver 1.8.9
CC:	djgpp-workers AT delorie DOT com
In-reply-to:	<1001931968.21287.12.camel@bender.falconsoft.be> (message from
	Tim Van Holder on 01 Oct 2001 12:26:07 +0200)
Subject:	Re: fixpath patch (rev 3)
References:	<200110010921 DOT LAA18740 AT lws256 DOT lu DOT erisoft DOT se> <1001931968 DOT 21287 DOT 12 DOT camel AT bender DOT falconsoft DOT be>
Reply-To:	djgpp-workers AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	djgpp-workers AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

> From: Tim Van Holder <tim DOT van DOT holder AT pandora DOT be>
> Date: 01 Oct 2001 12:26:07 +0200
> 
> Note that I would prefer /dev/[bogus] or something similar, to avoid
> any and all issues with colons (either as drive or path separator).

What issues are those?

If you are afraid of commands that fail, that's okay: we _want_ them
to fail when this happens.  We just want them to fail in the least
dangerous way.

As for "[bogus]", it is a valid file name, so, while extremely
improbable, it could exist on a user's machine.

I thought about other characters which are invalid in file names, but
all of them seem to run a risk of unintended consequences.  For
example, `*' and `?' could expand into something, `>' or `|' could
cause creation of files or even change the semantics of the command,
etc.  We could use control characters (below the blank), though.  If
someone has ideas, please speak up.

- Raw text -