From: Gerald Pfeifer <gerald@pfeifer.com>
To: Andre Majorel <aym-ccg@teaser.fr>, gcc-patches@gcc.gnu.org
Cc: gcc@gnu.org
Subject: [PATCH] for Re: C99 and C++0x status pages
Date: Mon, 09 May 2011 07:32:00 -0000 [thread overview]
Message-ID: <alpine.LNX.2.00.1105090231050.3911@gerinyyl.fvgr> (raw)
In-Reply-To: <20100831071013.GD26777@aym.net2.nerim.net>
On Tue, 31 Aug 2010, Andre Majorel wrote:
> Yesterday, I spent an hour looking for the C99 and C++0x status
> pages in http://gcc.gnu.org/,
>
> http://gcc.gnu.org/c99status.html
> http://gcc.gnu.org/projects/cxx0x.html
>
> Apparently, the shortest path to the latter is
>
> "Releases"
> -> "GCC 4.5.1"
> -> "GCC 4.5.1 Jul 31, 2010 (changes)"
> -> "Improved experimental support for the upcoming C++0x"
> -> "please see the C++0x in GCC project page"
>
> Those are among the most useful pages of the site, it makes no
> sense to bury them 4+ levels deep.
You're right, these two are really nice and for lack of proper landing
pages for the C and C++ languages I went ahead and committed the patch
below.
Thanks for pointing this out, and sorry for the "slight" delay in getting
back to you.
Gerald
Index: index.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/index.html,v
retrieving revision 1.800
diff -u -r1.800 index.html
--- index.html 1 May 2011 21:26:47 -0000 1.800
+++ index.html 9 May 2011 00:30:51 -0000
@@ -15,7 +15,9 @@
<img src="img/gccegg-65.png" alt="" align="right" />
<p>The GNU Compiler Collection includes front ends for
-C, C++, Objective-C, <a href="fortran/">Fortran</a>,
+<a href="c99status.html">C</a>,
+<a href="projects/cxx0x.html">C++</a>,
+Objective-C, <a href="fortran/">Fortran</a>,
<a href="java/">Java</a>, Ada, and Go, as well as libraries for these
languages (<a href="libstdc++/">libstdc++</a>, libgcj,...).
GCC was originally written as the compiler for the <a
parent reply other threads:[~2011-05-09 0:34 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20100831071013.GD26777@aym.net2.nerim.net>]
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=alpine.LNX.2.00.1105090231050.3911@gerinyyl.fvgr \
--to=gerald@pfeifer.com \
--cc=aym-ccg@teaser.fr \
--cc=gcc-patches@gcc.gnu.org \
--cc=gcc@gnu.org \
/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).