Message-Id: <199702242254.HAA19056@mail.st.rim.or.jp>
From: "Daisuke Aoyama" <jack AT st DOT rim DOT or DOT jp>
To: "Eli Zaretskii" <eliz AT is DOT elta DOT co DOT il>
Cc: "Alexander V. Lukyanov" <lav AT video DOT yars DOT free DOT net>,
        <djgpp-workers AT delorie DOT com>
Subject: RE: bashb7.zip is now available.
Date: Tue, 25 Feb 1997 07:21:49 +0900
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Eli Zaretskii <eliz AT is DOT elta DOT co DOT il> wrote:
> Alas, `_put_path' is not where the problems are.  The knowledge about
> what a Microsoft-style pathname looks like is scattered across the
> entire library in the various filename-related functions, which will
> all have to be rewritten.  Some examples are `_fixpath', `stat',
> `opendir', `rename'... do I need to continue?

I understand. No, thank you.

> And btw, pushing the //d/ feature into DJGPP's libc will mean that
> non-DJGPP programs will break when you set PATH_SEPARATOR=: which is
> hardly desired, since people use `bash' as their primary interactive
> shell.

I think peoples needing to use  //d/ or colon separator are smaller.
I wish them to be careful about non-DJGPP programs.
Then DJGPP's libc supports it as hidden feature.
Or if possible, I want to support network paths(UNCs) with it.

Daisuke Aoyama
jack AT st DOT rim DOT or DOT jp