Message-ID: <1091.192.168.0.12.1139752324.squirrel@mail.morrison.mine.nu>
In-Reply-To: <20060212115826.GR14219@calimero.vinschen.de>
References: <20060210190116.GL14219@calimero.vinschen.de>     <2A9FABB3664AF8459CBADA1CE4E402463D1BF1@DF-MASTIFF-MSG.exchange.corp.microsoft.com>     <20060211204153.GA14065@trixie.casa.cgf.cx>     <1139.192.168.0.12.1139733885.squirrel@mail.morrison.mine.nu>     <20060212115826.GR14219@calimero.vinschen.de>
Date: Sun, 12 Feb 2006 13:52:04 -0000 (GMT)
Subject: Re: default PATH
From: "John Morrison" <john@morrison.mine.nu>
To: cygwin@cygwin.com
Reply-To: john@morrison.mine.nu
User-Agent: SquirrelMail/1.4.5
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

On Sun, February 12, 2006 11:58 am, Corinna Vinschen wrote:
> On Feb 12 08:44, John Morrison wrote:
>> On Sat, February 11, 2006 8:41 pm, Christopher Faylor wrote:
>> > We're
>> > just trying go figure out if removing the ;; translation will affect
>> > many people.  We're not looking to add things to the PATH.
>> >
>> > There is a tradeoff here and I don't believe that we really know what
>> > the implications are.  You can speculate that thousands of people are
>> > affected by the ;; problem but we haven't had very many complaints
>> about
>> > this and certainly people who are relying on ;; are not going to be
>> > sending email here since Cygwin is working as they expect.
>> >
>> > Also, while skipping empty elements is a trivial operation, it is not
>> > without cost.  Every time that we have to guard the user against
>> > something like this, we add another nail to the "cygwin is slow"
>> coffin.
>>
>> Would a reasonable solution would be to make the PATH environment
>> variable
>> a special case and parse it when set?  (Appologies if this isn't a
>> reasonable solution)
>
> Er... how does this match the question?  %PATH% always exists and so
> it has always to be parsed to create $PATH.

Humm, sorry - sleep deprived.  Was thinking that it would only need to be
parsed once (don't know the internals of cygwin very well) rather than the
(possibily, if I read correcly, implied) multiple times.

J.


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/