This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: [using gcc book] ch1 rewrite
- From: "Zack Weinberg" <zack at codesourcery dot com>
- To: Chris Devers <cdevers at pobox dot com>
- Cc: GCC list <gcc at gcc dot gnu dot org>
- Date: Tue, 02 Sep 2003 11:45:24 -0700
- Subject: Re: [using gcc book] ch1 rewrite
- References: <Pine.OSX.4.56.0309021024570.9933@macdaddy.local>
Chris Devers <cdevers@pobox.com> writes:
> (Substantially a re-post of a message from yesterday.)
>
> I've prepared a significant rewrite of frontends.texi, which constitutes
> chapter 1 of the _Using GCC_ book.
>
> I would like to solicit commentary on whether this revised text is clear,
> technically accurate, and gets the important points across succinctly.
>
> The deadline for submitting the manuscript is *TODAY*, so any notes at all
> ("yes it's fine, print it", "no leave it all alone", etc) would be nice :)
This reads well to me. I just have one nit:
> The abbreviation @dfn{GCC} has multiple meanings in common use.
> Historically, the abbreviation stood for ``GNU C Compiler''; this sense
> of the name is still common when the emphasis is on compiling C programs.
> However, the name is now defined generically for the compiler collection
> as a whole, referring to all languages supported by the suite.
The second sentence here reads awkwardly. I would suggest instead
| The current official meaning is ``GNU Compiler Collection'', which
| refers generically to the complete suite of supported languages.
zw