Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin-developers AT sourceware DOT cygnus DOT com From: Chris Faylor Date: Fri, 19 May 2000 17:09:02 -0400 To: cygwin-developers AT sourceware DOT cygnus DOT com Subject: Re: cr/lf conundrum Message-ID: <20000519170902.B21946@cygnus.com> Reply-To: cygwin-developers AT sourceware DOT cygnus DOT com Mail-Followup-To: cgf AT cygnus DOT com, cygwin-developers AT sourceware DOT cygnus DOT com References: <200005192027 DOT QAA20516 AT envy DOT delorie DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.1.12i In-Reply-To: <200005192027.QAA20516@envy.delorie.com>; from dj@delorie.com on Fri, May 19, 2000 at 04:27:07PM -0400 On Fri, May 19, 2000 at 04:27:07PM -0400, DJ Delorie wrote: >There are a couple of things I can do to prevent this type of problem >in the future (namely, making getc/putc *not* be macros), but I can't >think of a good solution to handle existing applications. I can think >of many hacks, but they all have drawbacks. > >Ideas? This is a tough one. The only "solution" that I see is to somehow keep (p)->_r at 0 and always revert to using __srget(p) to retrieve the character. This would involve some very creative bookkeeping in parallel with with the stdio structure, though, I think. Bleah. cgf