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 To: cygwin AT cygwin DOT com From: Eric Blake Subject: Re: Unwanted .exe appended to symlinks Date: Sat, 9 Jul 2005 16:50:07 +0000 (UTC) Lines: 21 Message-ID: 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-Transfer-Encoding: 7bit User-Agent: Loom/3.14 (http://gmane.org/) X-IsSubscribed: yes 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. But yes, we are in violent agreement, and I have posted an upstream bug-fix request to get the output of dirname(1) fixed in coreutils. -- Eric Blake -- 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/