On 9 March 2011 00:46, Karl Berry <[email protected]> wrote: > > Great. I'll appreciate a patch.
Attached, against CVS head. I have rewritten section 5.7 to bring it
up to date, with the following underlying reasoning:
1. It's usually safe to assume C89 & POSIX-1.1993.
2. You can use gnulib to get much of C99 & POSIX-1.2001, and even some
of POSIX-1.2008 & GNU. It has lots of other useful stuff; you should
pretty much always use it.
3. Where possible, one should stick to standards.
I have removed some material from section 5.6: secondly, an
out-of-date example of the use of gnulib, but first, a section that
starts: "It used to be ok to not worry about the difference between
pointers and integers when passing arguments to functions. However, on
most modern 64-bit machine pointers are wider than @code{int}." At
first glance, this is still important (there are still plenty of
32-bit systems), but in fact, if you read further, the point of this
passage is "use prototypes", which I think we can safely say is a
learnt lesson nowadays. 32-bit vs 64-bit issues are covered elsewhere.
I've done my best to keep the GNU voice without resorting to method
acting, but obviously feel free to edit for consistency of style.
--
http://rrt.sc3d.org
standards.texi.patch
Description: Binary data
