From: "Tim Van Holder" <tim DOT van DOT holder AT pandora DOT be>
To: <djgpp-workers AT delorie DOT com>
Cc: <snowball3 AT bigfoot DOT com>, <sandmann AT clio DOT rice DOT edu>
Subject: Re: Bash 2.05 beta of 28-Aug-2001 query
Date: Sat, 1 Sep 2001 23:35:14 +0200
Message-ID: <000401c1332d$fc666b40$2a8ce0d5@pandora.be>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.2627
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
In-Reply-To: <7458-Sat01Sep2001204232+0300-eliz@is.elta.co.il>
Importance: Normal
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
Precedence: bulk

> > > ! gcc_version_trigger = /dev/c/dj204/gnu/gcc-2.953/gcc/version.c
> > > --- 22 ----
> > > ! gcc_version_trigger = /dj204/gnu/gcc-2.953/gcc/version.c
> > 
> > The only difference here is that somehow the path was made
> > completely absolute (maybe an extra pwd call somewhere); this may
> > be an internal bash change.  In any case, it's probably harmless.
> 
> I'm not sure: this path will stop working if something during the
> build switches to another drive.  For that reason, it is IMHO unsafe
> for Bash to remove the drive letter, because it cannot possibly know
> what purposes would that path serve.

My bad - I mistakenly thought the /dev/c was added, not removed.  In
that case, indeed it is not a change for the better.

> > > ! ac_cv_path_install=${ac_cv_path_install='ginstall -c'}
> > > --- 115 ----
> > > ! ac_cv_path_install=${ac_cv_path_install=$'ginstall -c'}
> > 
> > This is probably a bash quirk as well ($'foo' is bash shorthand for
> > "the localized version of the string 'foo'", I think).
> 
> ??? You mean $foo can stand for something other than the value of
> variable foo?

No, but $'foo' might.
From the NEWS file that comes with bash 2.04:

j.  There are more internationalization features; bash uses gettext if
    it is available.  The $"..." translation syntax uses the current
    locale and gettext.

So $'blah' might be similar; not sure why bash would suddenly emit
that though.