From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18984 invoked by alias); 24 Sep 2004 12:23:26 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 18969 invoked from network); 24 Sep 2004 12:23:24 -0000 Received: from unknown (HELO mx1.redhat.com) (66.187.233.31) by sourceware.org with SMTP; 24 Sep 2004 12:23:24 -0000 Received: from int-mx2.corp.redhat.com (int-mx2.corp.redhat.com [172.16.27.26]) by mx1.redhat.com (8.12.11/8.12.10) with ESMTP id i8OCNJHd007343 for ; Fri, 24 Sep 2004 08:23:19 -0400 Received: from potter.sfbay.redhat.com (potter.sfbay.redhat.com [172.16.27.15]) by int-mx2.corp.redhat.com (8.11.6/8.11.6) with ESMTP id i8OCNI700390 for ; Fri, 24 Sep 2004 08:23:18 -0400 Received: from cygbert.vinschen.de (vpn50-1.rdu.redhat.com [172.16.50.1]) by potter.sfbay.redhat.com (8.11.6/8.11.6) with ESMTP id i8OCNHV06225 for ; Fri, 24 Sep 2004 05:23:17 -0700 Received: by cygbert.vinschen.de (Postfix, from userid 500) id 0F4E95808D; Fri, 24 Sep 2004 14:24:07 +0200 (CEST) Date: Fri, 24 Sep 2004 12:23:00 -0000 From: Corinna Vinschen To: gdb-patches@sources.redhat.com Subject: Re: [RFC] Suggested ways to remove the need for xm-go32.h Message-ID: <20040924122406.GA10888@cygbert.vinschen.de> Reply-To: gdb-patches@sources.redhat.com Mail-Followup-To: gdb-patches@sources.redhat.com References: <01c49d82$Blat.v2.2.2$23875ec0@zahav.net.il> <20040923050534.GA11936@trixie.casa.cgf.cx> <200409232058.i8NKwHg4009186@elgar.sibelius.xs4all.nl> <20040923211643.GA22829@trixie.casa.cgf.cx> <01c4a223$Blat.v2.2.2$e47a6c80@zahav.net.il> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <01c4a223$Blat.v2.2.2$e47a6c80@zahav.net.il> User-Agent: Mutt/1.4.2i X-SW-Source: 2004-09/txt/msg00395.txt.bz2 On Sep 24 12:46, Eli Zaretskii wrote: > > Out of curiousity is O_BINARY mandated by ISO C? I suspect not. > > O_BINARY is a Posix thing (ANSI C doesn't know about `open' at all), > so ISO C has nothing to say about it. But even if you look at the > latest Posix (well, the draft I have here), you will not find O_BINARY > there. So Posix systems are not allowed to distinguish between text > and binary files. That's nothing GDB should be concerned of, probably, but that's definitely a leak in the definitions. How much sense does it make to allow "b" in fopen but no equivalent in the low-level interface :-( Corinna -- Corinna Vinschen Cygwin Project Co-Leader Red Hat, Inc.