Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
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
From:	"Dave Korn" <dave DOT korn AT artimi DOT com>
To:	<cygwin AT cygwin DOT com>
Subject:	RE: Problem with sh/bash and snapshot cygwin1-20050825.dll
Date:	Fri, 26 Aug 2005 15:55:18 +0100
MIME-Version:	1.0
In-Reply-To:
Message-ID:	<SERRANOjJeKBnZZkO7m0000032d@SERRANO.CAM.ARTIMI.COM>

----Original Message----
>From: Dave Korn
>Sent: 26 August 2005 15:52

> ----Original Message----
>> From: Christopher Faylor
>> Sent: 26 August 2005 15:48
> 
>> On Fri, Aug 26, 2005 at 06:17:13AM -0600, Eric Blake wrote:
>>> While you're at it, fix realpath(NULL, buf) to set buf[0]='\0', instead
>>> of leaving garbage there.
>> 
>> What's the rationale for touching buf when realpath is returning an
>> error and setting EINVAL? 
>> 
>> cgf
> 
>   Standards-mandated leeway?


... plus of course it means you can call strlen on the buffer without having
to check errno first ...


    cheers,
      DaveK
-- 
Can't think of a witty .sigline today....


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

- Raw text -