Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sourceware.cygnus.com Delivered-To: mailing list cygwin@sourceware.cygnus.com From: Chris Faylor Date: Fri, 9 Jun 2000 12:40:45 -0400 To: "'cygwin@sourceware.cygnus.com'" Subject: Re: New version of setup.exe with fixes for i686-pc-cygwin/* prob lem Message-ID: <20000609124045.B23003@cygnus.com> Reply-To: cygwin@sourceware.cygnus.com Mail-Followup-To: "'cygwin@sourceware.cygnus.com'" References: <17B78BDF120BD411B70100500422FC6309E056@IIS000> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <17B78BDF120BD411B70100500422FC6309E056@IIS000>; from Dautrevaux@microprocess.com on Fri, Jun 09, 2000 at 06:07:25PM +0200 On Fri, Jun 09, 2000 at 06:07:25PM +0200, Bernard Dautrevaux wrote: >Chris, do I understand correctly that above, when saying "read text, write >binary" you are speaking about the default mode for open's where neither >O_TEXT nor O_BINARY are specified? otherwise reading a file in text mode >then switching to binary when writing the same file will most probably give >quite weird results ;-( I'm talking about the default behavior. We wouldn't change the way either O_TEXT or O_BINARY work. cgf -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe@sourceware.cygnus.com