Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
| From | Keith Thompson <kst-u@mib.org> |
|---|---|
| Newsgroups | comp.std.c |
| Subject | Misleading reference to "extended integer types" in foreword |
| Date | 2011-07-13 12:31 -0700 |
| Organization | None to speak of |
| Message-ID | <lntyaqq8no.fsf@nuthaus.mib.org> (permalink) |
The Foreword of the C99 standard includes an informal list of the
changes from C90/C95 to C99. It includes the following:
-- extended integer types and library functions in <inttypes.h>
and <stdint.h>
This could imply that the types defined in <stdint.h> (such as int32_t)
are "extended integer types" in the sense defined in 6.2.5. In fact,
they're typically typedefs for standard integer types (though they *can*
be typedefs for extended integer types).
I suggest that that bullet point should be split into two, one for the
optional extended integer types defined in 6.2.5, and one for
<inttypes.h> and <stdint.h>.
A couple of other minor things I noticed (one of which I think I've
already mentioned):
In the Foreword, "mixed declarations and code" would be clearer as
"mixed declarations and statements". (Declarations are code.)
In 6.2.5p7:
The standard signed integer types and standard unsigned integer
types are collectively called the _standard integer types_,
the extended signed integer types and extended unsigned integer
types are collectively called the _extended integer types_.
the comma should be a semicolon (or it could be two sentences).
(All of these are still present in N1570.)
--
Keith Thompson (The_Other_Keith) kst-u@mib.org <http://www.ghoti.net/~kst>
Nokia
"We must do something. This is something. Therefore, we must do this."
-- Antony Jay and Jonathan Lynn, "Yes Minister"
Back to comp.std.c | Previous | Next | Find similar | Unroll thread
Misleading reference to "extended integer types" in foreword Keith Thompson <kst-u@mib.org> - 2011-07-13 12:31 -0700
csiph-web