X-Spam-Check-By: sourceware.org
Date: Sun, 12 Feb 2006 12:58:26 +0100
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: default PATH
Message-ID: <20060212115826.GR14219@calimero.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <20060210190116 DOT GL14219 AT calimero DOT vinschen DOT de> <2A9FABB3664AF8459CBADA1CE4E402463D1BF1 AT DF-MASTIFF-MSG DOT exchange DOT corp DOT microsoft DOT com> <20060211204153 DOT GA14065 AT trixie DOT casa DOT cgf DOT cx> <1139 DOT 192 DOT 168 DOT 0 DOT 12 DOT 1139733885 DOT squirrel AT mail DOT morrison DOT mine DOT nu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1139.192.168.0.12.1139733885.squirrel@mail.morrison.mine.nu>
User-Agent: Mutt/1.4.2i
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

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.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

--
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/