Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Sat, 9 Jul 2005 19:09:10 +0200 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: Unwanted .exe appended to symlinks Message-ID: <20050709170910.GU7507@calimero.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <1120880636 DOT 6400 DOT 7 DOT camel AT localhost DOT localdomain> <42CFD190 DOT 2060109 AT byu DOT net> <20050709153641 DOT GR7507 AT calimero DOT vinschen DOT de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2i On Jul 9 16:50, Eric Blake wrote: > Corinna Vinschen cygwin.com> writes: > > > > > On Jul 9 07:30, Eric Blake wrote: > > > Hmm, while I'm at it, "dirname //" should return //, not /. > > > > No. // is a perfectly valid root dir in a system which differs between > > / and //. Let dirname(1) just use what it gets from dirname(3). > > > > Corinna > > > > Actually, dirname(1) doesn't call dirname(3) - there are enough quirks in > various platforms' dirname(3), plus POSIX requires the algorithm of dirname(1) > to work even on invalid pathnames. That's how Cygwin's dirname is designed. It also allows dirname on DOS paths. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader mailto:cygwin AT cygwin DOT com Red Hat, Inc. -- 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/