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:	<000f01c112ac$9d95ce40$806410ac@local>
From:	"Robert Collins" <robert DOT collins AT itdomain DOT com DOT au>
To:	"Trevor Forbes" <trevorforbes AT ozemail DOT com DOT au>,
	"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> <118b01c1125e$e4739390$0300a8c0 AT ufo>
Subject:	Re: Linking to cygwin1.dll and msvcrt.dll ?
Date:	Sun, 22 Jul 2001 22:48:31 +1000
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
X-OriginalArrivalTime:	22 Jul 2001 12:34:59.0882 (UTC) FILETIME=[B8E4B0A0:01C112AA]

----- Original Message -----
From: "Trevor Forbes" <trevorforbes AT ozemail DOT com DOT au>
> >
> > 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

The harm is that every added feature requires maintenance (to prevent
bitrot). If the feature is not really helpful (and we can debate the merits
of this particular feature ad nauseum) then you are adding to the
maintenance workload for few returns.

> end will help programmers, port and maintain programs more easily. Is that

These don't help porters from unix - they help folk who ported to pure win32
first, and now want cygwin support. In most cases a __CYGWIN__ won't be
needed because cygwin by default doesn't define WIN32 - thus their win32
code won't be activated.

> not the purpose of Cygwin. Anything that reduces the addition of #ifdef
> __CYGWIN__ would be a "smart" move in my humble opinion.

Sure - for porting _from unix_. IMO.


> Trevor
>

BTW: An alternative solution was suggested by Mumit - the creation of a
msvcrt compatability package that could include such macros - and wouldn't
involve creeping featurism. - I support such an approach.

Rob


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