Date: Wed, 18 Mar 2009 11:13:43 -0400
From: Christopher Faylor <cgf-use-the-mailinglist-please@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: _set_fmode?
Message-ID: <20090318151343.GB3581@ednor.casa.cgf.cx>
Reply-To: cygwin@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
References: <49C04B2D.2090703@cwilson.fastmail.fm> <20090318094323.GA12824@calimero.vinschen.de> <49C0EC08.8020907@cwilson.fastmail.fm> <20090318144112.GC16595@calimero.vinschen.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20090318144112.GC16595@calimero.vinschen.de>
User-Agent: Mutt/1.5.16 (2007-06-09)
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

On Wed, Mar 18, 2009 at 03:41:12PM +0100, Corinna Vinschen wrote:
>On Mar 18 08:41, Charles Wilson wrote:
>> Corinna Vinschen wrote:
>> > On Mar 17 21:15, Charles Wilson wrote:
>> >>
>> >> +#if defined(_WIN32) && !defined(__CYGWIN__)
>> 
>> > The !defined(__CYGWIN__) is not necessary because gcc for Cygwin
>> > doesn't define _WIN32.
>> 
>> gcc does not define it. But the w32api headers DO.
>
>Hmpf, right.
>
>> >   extern int _fmode;
>> >   _fmode = O_BINARY;
>> 
>> I didn't know you could access it directly, outside of cygwin1.dll.
>
>Well, it's defined in the application itself.
>
>> > But anyway, using binmode.o is much more elegant, IMHO.  I don't see
>> > what speaks against using it.
>> 
>> Well, now that I see libbinmode.a, nothing.
>
>Don't use the libFOOmode.a files.  They don't do what you want.
>Actually I think we should remove them better sooner than later.

No, I've always meant to make these work as planned.  It is possible but
I've never gotten around to it since I created them.

cgf

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