From: ams@gnu.org (Alfred M. Szmidt)
To: Joel Brobecker <brobecker@adacore.com>
Cc: jan.kratochvil@redhat.com, gdb-patches@sourceware.org
Subject: Re: [no-commit-intention] Naive unnamed fields for main_type [Re: [patch] Fix gdb-gdb.py for flds_bnds copy-pastes]
Date: Thu, 09 Feb 2012 19:07:00 -0000 [thread overview]
Message-ID: <E1RvZKZ-0004ee-Tm@fencepost.gnu.org> (raw)
In-Reply-To: <20120209151621.GB3474@adacore.com> (message from Joel Brobecker on Thu, 9 Feb 2012 07:16:21 -0800)
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.
next prev parent reply other threads:[~2012-02-09 19:07 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-09 9:28 [patch] Fix gdb-gdb.py for flds_bnds copy-pastes Jan Kratochvil
2012-02-09 9:32 ` [no-commit-intention] Naive unnamed fields for main_type [Re: [patch] Fix gdb-gdb.py for flds_bnds copy-pastes] Jan Kratochvil
2012-02-09 15:16 ` Joel Brobecker
2012-02-09 15:37 ` Jan Kratochvil
2012-02-09 18:56 ` Eli Zaretskii
2012-02-10 18:05 ` Tom Tromey
2012-02-10 19:01 ` Jan Kratochvil
2012-02-10 19:22 ` Tom Tromey
2012-02-10 19:29 ` Jan Kratochvil
2012-02-12 10:20 ` Mark Kettenis
2012-02-12 19:23 ` Jan Kratochvil
2012-02-09 19:07 ` Alfred M. Szmidt [this message]
2012-02-09 19:23 ` Stan Shebs
2012-02-10 18:07 ` Tom Tromey
2012-02-09 15:12 ` [patch] Fix gdb-gdb.py for flds_bnds copy-pastes Joel Brobecker
2012-02-09 15:15 ` [commit] " Jan Kratochvil
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E1RvZKZ-0004ee-Tm@fencepost.gnu.org \
--to=ams@gnu.org \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox