public inbox for libc-hacker@sourceware.org
 help / color / mirror / Atom feed
From: Roland McGrath <roland@redhat.com>
To: GNU libc hackers <libc-hacker@sources.redhat.com>
Subject: -std=gnu99
Date: Fri, 11 Oct 2002 04:51:00 -0000	[thread overview]
Message-ID: <200210111103.g9BB3U425922@magilla.sf.frob.com> (raw)

I've made libc compile using -std=gnu99 now.  This didn't require changing
any code (nor was it required to make any code work), though some tiny nits
were changed because of new warnings.  It just keeps us on our toes and
reflects the fact that ISO C99 with GNU extensions is the dialect in which
libc is written.  In writing new libc code we are free to use C99
constructs that GCC's default mode (-std=gnu89) won't accept.

However, there are now some new spurious warnings about use of the `a' flag
in scanf formats.  GCC's format checker can't distinguish between the
pre-1999 GNU extension `a' flag for string formats and the ISO C99 new `a'
format specifier for floats, and under -std=gnu99 it sees any format
starting with `%a' as the latter.  The runtime format parser has no trouble
with either, and no valid syntax is actually ambiguous. 

                 reply	other threads:[~2002-10-11 11:03 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=200210111103.g9BB3U425922@magilla.sf.frob.com \
    --to=roland@redhat.com \
    --cc=libc-hacker@sources.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).