Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT sources DOT redhat DOT com>
List-Help:	<mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT sources DOT redhat DOT com
Delivered-To:	mailing list cygwin AT sources DOT redhat DOT com
Message-ID:	<118b01c1125e$e4739390$0300a8c0@ufo>
From:	"Trevor Forbes" <trevorforbes AT ozemail DOT com DOT au>
To:	"Cygwin" <cygwin AT cygwin DOT com>
References:	<Pine DOT SOL DOT 3 DOT 91 DOT 1010721141254 DOT 14945C-100000 AT cse DOT cygnus DOT com> <053201c11242$c07ddca0$806410ac AT local>
Subject:	Re: Linking to cygwin1.dll and msvcrt.dll ?
Date:	Sun, 22 Jul 2001 13:02:09 +0930
MIME-Version:	1.0
X-Priority:	3
X-MSMail-Priority:	Normal
X-Mailer:	Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE:	Produced By Microsoft MimeOLE V5.50.4522.1200

>
> > I am not in a position to judge "creeping feature'ism". It is
> > just that these 4 *ex methods are documented and are even
> > suggested in the Microsoft documentation. If this memory
> > leak is not a problem in Cygwin, then these functions
> > should be really easy to implement since they would just
> > call the Win32 APIs.
>
> They are suggested to work around MS's inability to write high-quality
code.
> The calls would be easy to implement yes, but there is no point in putting
> them in *cygwin*.
>
> Rob
>

I agree with Mo.  What is the harm in adding "minor" functions which in the
end will help programmers, port and maintain programs more easily. Is that
not the purpose of Cygwin. Anything that reduces the addition of #ifdef
__CYGWIN__ would be a "smart" move in my humble opinion.

Trevor



--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -