9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Douglas A. Gwyn" <DAGwyn@null.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] C99
Date: Wed, 28 Feb 2001 09:30:25 +0000	[thread overview]
Message-ID: <3A9C9643.FF73D120@null.net> (raw)
In-Reply-To: <20010227142543.C81F2199EE@mail.cse.psu.edu>

Russ Cox wrote:
> http://www.dkuug.dk/JTC1/SC22/WG14/www/docs/n843.ps.gz

That's not an accurate copy of the 1999 C standard.
Jack Klein just posted information in comp.lang.c.moderated
about obtaining a correct copy.

There are several sources for a summary of the main changes
from C89 to C99, e.g.
http://web.onetelnet.ch/~twolf/tw/c/c9x_changes.html

The preprocessor extensions are easy enough to implement,
except possibly for the variable-number-of-arguments facility.

Several of the extensions to the language proper are either
already in Plan 9's compiler (compound literals, designated
initializers) or else are straightforward to add.  Variable-length
arrays might be harder.

Most of the library extensions are straightforward to add.
For a start at providing some C99 standard library facilities,
e.g. <stdbool.h> and <stdint.h>, see
http://www.lysator.liu.se/c/q8/index.html
The most difficult one is undoubtedly <tgmath.h>, which
requires compiler support.

My opinion as a long-time implementor and maintainer of C
environments is that *most* of the changes from C89 to C99
can be implemented merely by taking the time to do it,
without having to think very hard, and just a few features
require special care (VLAs, <tgmath.h>).  Until C99 conforming
implementations reach the marketplace and start to be used,
there won't be any demand for the new features.  That means
in probably another year or two it would be useful to have C99
support ready.


  reply	other threads:[~2001-02-28  9:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-27 14:25 Russ Cox
2001-02-28  9:30 ` Douglas A. Gwyn [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-10-04 18:34 Joel “chesky” Salomon
2006-10-04 19:24 ` erik quanstrom
2001-02-28  2:51 okamoto
2001-02-27 14:27 forsyth
2001-02-27 13:19 Russ Cox
2001-02-27 13:18 rob pike
2001-02-27 13:12 Russ Cox
2001-02-27 10:43 David Rubin

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=3A9C9643.FF73D120@null.net \
    --to=dagwyn@null.net \
    --cc=9fans@cse.psu.edu \
    /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 NNTP newsgroup(s).