Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-developers-subscribe AT sourceware DOT cygnus DOT com>
List-Archive: <http://sourceware.cygnus.com/ml/cygwin-developers/>
List-Post: <mailto:cygwin-developers AT sourceware DOT cygnus DOT com>
List-Help: <mailto:cygwin-developers-help AT sourceware DOT cygnus DOT com>, <http://sourceware.cygnus.com/ml/#faqs>
Sender: cygwin-developers-owner AT sourceware DOT cygnus DOT com
Delivered-To: mailing list cygwin-developers AT sourceware DOT cygnus DOT com
Date: Fri, 19 May 2000 17:18:15 -0400
Message-Id: <200005192118.RAA20889@envy.delorie.com>
From: DJ Delorie <dj AT delorie DOT com>
To: earnie_boyd AT yahoo DOT com
CC: cygwin-developers AT sourceware DOT cygnus DOT com
In-reply-to: <20000519204415.27070.qmail@web115.yahoomail.com> (message from
	Earnie Boyd on Fri, 19 May 2000 13:44:15 -0700 (PDT))
Subject: Re: cr/lf conundrum
References:  <20000519204415 DOT 27070 DOT qmail AT web115 DOT yahoomail DOT com>


> After investigating stdio.h I see that getc/putc are already prototyped as
> functions.  The getc/putc macros are conditioned with `#ifndef lint' already. 
> This could be modified to also condition __CYGWIN__ or give instructions to use
> `-Dlint' in CFLAGS.

The problem isn't that they're macros *now*.  The problem is that they
were macros back when the existing apps were built, like the bash on
sourceware.  If we could recompile the world, it wouldn't be a
problem.  I am, however, considering de-macroizing them in case this
happens again, even though there's a minor speed penalty when that
happens.

I'm working on a patch that uses api_major/api_minor (which I just
remembered we had :) to detect these legacy apps, and try to adjust
the conversion logic accordingly.