From: "Joseph S. Myers" <jsm28@cam.ac.uk>
To: Zack Weinberg <zack@codesourcery.com>
Cc: <gcc@gcc.gnu.org>
Subject: Re: Proposal
Date: Wed, 19 Sep 2001 01:14:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.33.0109190901050.21114-100000@kern.srcf.societies.cam.ac.uk> (raw)
In-Reply-To: <20010918221948.I12089@codesourcery.com>
On Tue, 18 Sep 2001, Zack Weinberg wrote:
> I'm not sure of this; would they be useful to normal users of GCC?
> Standardization proposals tend to be written in standardese and
> therefore are not suitable as end-user documentation.
They're just as suitable as the standards themselves are - and the
standards themselves *ought* to be being used for reference by every
serious programmer in standardised languages. (Though this doesn't remove
the use of existing tutorial material in the manual and of bodies of code
with idiomatic uses of the extensions for users to read and learn from;
nor do I claim that the optimal method for all users of *learning* C or
C++ is to read ISO 9899 or ISO 14882.) Of course the proposals would
include the rationale for the changes as well as the actual textual
changes to the standard.
--
Joseph S. Myers
jsm28@cam.ac.uk
next prev parent reply other threads:[~2001-09-19 1:14 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-15 11:45 Proposal Frank Klemm
2001-09-15 12:15 ` Proposal Gerald Pfeifer
2001-09-17 16:00 ` Proposal Neil Booth
2001-09-18 2:30 ` Proposal Joseph S. Myers
2001-09-18 10:21 ` Proposal Zack Weinberg
2001-09-18 11:14 ` Proposal Joseph S. Myers
2001-09-18 22:20 ` Proposal Zack Weinberg
2001-09-19 1:14 ` Joseph S. Myers [this message]
2001-09-18 12:23 ` Proposal Frank Klemm
2001-09-18 22:37 ` Proposal Zack Weinberg
2001-09-19 0:02 ` Proposal Neil Booth
2001-09-19 2:23 ` Proposal Tim Hollebeek
2001-09-19 2:41 ` Proposal Richard Earnshaw
2001-09-19 13:38 ` Proposal Joe Buck
2001-09-18 15:35 ` Proposal Robert Lipe
2001-09-18 16:59 ` Proposal Russ Allbery
2001-09-20 11:17 ` Proposal Kai Henningsen
2001-09-20 12:34 ` Proposal Russ Allbery
2001-09-18 9:48 ` Proposal Frank Klemm
2001-09-18 11:06 ` Proposal Neil Booth
2001-09-18 11:37 ` Proposal Kevin Handy
2001-09-18 15:48 ` Proposal Neil Booth
2001-09-18 15:55 ` Proposal Toon Moene
2001-09-27 5:39 ` Proposal Alexandre Oliva
2001-09-27 7:09 ` Proposal Frank Klemm
2001-09-27 16:22 ` Proposal Zack Weinberg
2001-09-29 15:45 ` Proposal Frank Klemm
2001-09-30 9:35 ` Proposal Zack Weinberg
2001-09-27 16:36 ` Proposal Neil Booth
2001-09-29 15:45 ` Proposal Frank Klemm
2001-09-29 17:22 ` Proposal Daniel Jacobowitz
2001-09-29 18:32 ` OT: Proposal Michael Matz
2001-10-03 3:52 ` Proposal Fergus Henderson
2001-09-17 8:55 Proposal Thomas R. Truscott
2001-09-18 9:32 Proposal dewar
2001-09-18 12:30 Proposal dewar
2001-09-18 23:01 ` Proposal Zack Weinberg
2001-09-19 0:06 Proposal dewar
2001-09-19 2:34 Proposal dewar
2001-09-19 2:44 Proposal dewar
2012-09-03 15:16 Proposal Afeez Basit
2012-09-03 18:35 Proposal Afeez Basit
2013-06-26 17:41 Proposal Barrister David Lopez Esq
2013-06-26 18:15 ` Proposal Paolo Carlini
2013-06-26 18:40 ` Proposal Daniel Santos
2013-06-26 17:47 Proposal Barrister David Lopez Esq
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=Pine.LNX.4.33.0109190901050.21114-100000@kern.srcf.societies.cam.ac.uk \
--to=jsm28@cam.ac.uk \
--cc=gcc@gcc.gnu.org \
--cc=zack@codesourcery.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).