Date: Mon, 10 May 1999 09:33:06 +0300 (IDT)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: "Mark E." <snowball3 AT bigfoot DOT com>
cc: djgpp-workers AT delorie DOT com
Subject: RE: v2.03: wrapping up
In-Reply-To: <199905091945.TAA123402@out1.ibm.net>
Message-ID: <Pine.SUN.3.91.990510093248.2882B-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp-workers AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Sun, 9 May 1999, Mark E. wrote:

> I'm not sure if I've found a problem or not. Here's a case that produces 
> gibberish at the end of the output string when FOO doesn't exist:
> /dev/env/FOO~c:/djgpp

Strange: this test case works for me.  But you are right, the code is
dangerous, thanks for catching it.

> I missed the debate over the delimiter change while working on 
> changing my email address, but if it isn't too late I would suggest  " as 
> a possible delimiter, as in:
> /dev/env/DJDIR"c:/djgpp"/include

Not good: the quotes are removed by the shell and by the DJGPP startup
code.  So the quotes will never get to put_path, unless we quote the
quotes.  However, quoting the quotes will never work right in this
case, because every sub-shell invocation removes one level of quotes,
and you can never be sure how many sub-shells are involved in a given
shell script.