From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21606 invoked by alias); 9 Feb 2012 19:07:12 -0000 Received: (qmail 21595 invoked by uid 22791); 9 Feb 2012 19:07:10 -0000 X-SWARE-Spam-Status: No, hits=-1.7 required=5.0 tests=AWL,BAYES_00,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from fencepost.gnu.org (HELO fencepost.gnu.org) (140.186.70.10) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 09 Feb 2012 19:06:56 +0000 Received: from ams by fencepost.gnu.org with local (Exim 4.71) (envelope-from ) id 1RvZKZ-0004ee-Tm; Thu, 09 Feb 2012 14:06:55 -0500 Date: Thu, 09 Feb 2012 19:07:00 -0000 Message-Id: From: ams@gnu.org (Alfred M. Szmidt) To: Joel Brobecker CC: jan.kratochvil@redhat.com, gdb-patches@sourceware.org In-reply-to: <20120209151621.GB3474@adacore.com> (message from Joel Brobecker on Thu, 9 Feb 2012 07:16:21 -0800) Subject: Re: [no-commit-intention] Naive unnamed fields for main_type [Re: [patch] Fix gdb-gdb.py for flds_bnds copy-pastes] Reply-to: ams@gnu.org References: <20120209092727.GA2664@host2.jankratochvil.net> <20120209093119.GA2722@host2.jankratochvil.net> <20120209151621.GB3474@adacore.com> X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2012-02/txt/msg00155.txt.bz2 Personally, I don't know what the obstacles are for switching to C99 (technical, FSF policy?). GNU policy is that it is OK to use C99, from the GNU Coding Standards, Calling System Functions: | Historically, C implementations differed substantially, and many | systems lacked a full implementation of ANSI/ISO C89. Nowadays, | however, very few systems lack a C89 compiler and GNU C supports | almost all of C99. Similarly, most systems implement POSIX.1-1993 | libraries and tools, and many have POSIX.1-2001. | Hence, there is little reason to support old C or non-POSIX systems, | and you may want to take advantage of C99 and POSIX-1.2001 to write | clearer, more portable, or faster code. You should use standard | interfaces where possible; but if GNU extensions make your program | more maintainable, powerful, or otherwise better, don't hesitate to | use them. In any case, don't make your own declaration of system | functions; that's a recipe for conflict.