public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Paulo J. Matos" <pocm@soton.ac.uk>
To: gcc-help@gcc.gnu.org
Subject: On the C99 Status
Date: Sat, 22 Mar 2008 12:09:00 -0000	[thread overview]
Message-ID: <11b141710803220508q29483a6fr8d09c61bda062893@mail.gmail.com> (raw)

From http://gcc.gnu.org/gcc-4.3/c99status.html , I see several
features are still missing from gcc to fully adhere to the C99
standard.

Those worth mentioning for me are complex support and variable length
arrays, still there are other either missing or broken. This is of
interest to me because I tend to try to follow standards so I usually
compile my programs with -std=c99.
Now, I wonder why after so many years of having a standard out, why
there's still some c99 features missing.
I can only imagine that there isn't too much incentive into
implementing the missing features. The other possibility is that gcc,
as a big software beast, is getting so big that adding completely new
features might be quite hard... anyway, this is just me thinking out
loud.
I would like to hear what the current issue is with adding the missing
features to gcc if anyone cares to explain.

Cheers,

-- 
Paulo Jorge Matos - pocm at soton.ac.uk
http://www.personal.soton.ac.uk/pocm
PhD Student @ ECS
University of Southampton, UK
Sponsor ECS runners - Action against Hunger:
http://www.justgiving.com/ecsrunslikethewind

             reply	other threads:[~2008-03-22 12:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-22 12:09 Paulo J. Matos [this message]
2008-03-22 18:18 ` Martin Krischik
2008-03-22 18:53   ` Luke A. Guest
2008-03-23  8:18     ` Martin Krischik

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=11b141710803220508q29483a6fr8d09c61bda062893@mail.gmail.com \
    --to=pocm@soton.ac.uk \
    --cc=gcc-help@gcc.gnu.org \
    /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).