From: Mark Mitchell <mark@codesourcery.com>
To: Ian Lance Taylor <iant@google.com>
Cc: Diego Novillo <dnovillo@google.com>, gcc@gcc.gnu.org
Subject: Re: [tuples] API documentation
Date: Fri, 13 Jun 2008 19:24:00 -0000 [thread overview]
Message-ID: <4852C932.4070201@codesourcery.com> (raw)
In-Reply-To: <m3skviqvny.fsf@google.com>
Ian Lance Taylor wrote:
> I think that when it is reasonably stable it should move into a .texi
> file in the source code. That is there the gcc internals manual
> lives.
>
> I would not be averse to moving the entire internals manual to the web
> in some form. But having it in two places does not seem like a good
> idea to me.
I agree. And, I think in the source code is the right answer, even over
the long term. For one thing, one often needs to know what the API
*was* for some old version of GCC.
--
Mark Mitchell
CodeSourcery
mark@codesourcery.com
(650) 331-3385 x713
prev parent reply other threads:[~2008-06-13 19:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-12 18:47 Diego Novillo
2008-06-12 19:54 ` Ian Lance Taylor
2008-06-13 19:24 ` Mark Mitchell [this message]
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=4852C932.4070201@codesourcery.com \
--to=mark@codesourcery.com \
--cc=dnovillo@google.com \
--cc=gcc@gcc.gnu.org \
--cc=iant@google.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).