public inbox for gcc-cvs-wwwdocs@sourceware.org
help / color / mirror / Atom feed
From: Eric Gallager <egallager@sourceware.org>
To: gcc-cvs-wwwdocs@gcc.gnu.org
Subject: gcc-wwwdocs branch master updated. dbaebcd450925b622572944dcb34b26b76466c26
Date: Fri, 19 Nov 2021 13:12:28 +0000 (GMT)	[thread overview]
Message-ID: <20211119131228.72EE0385AC0A@sourceware.org> (raw)

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "gcc-wwwdocs".

The branch, master has been updated
       via  dbaebcd450925b622572944dcb34b26b76466c26 (commit)
      from  ba66d93e131a74ccc0fa4551b9a288ec38556ddc (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit dbaebcd450925b622572944dcb34b26b76466c26
Author: Eric Gallager <egall@gwmail.gwu.edu>
Date:   Fri Nov 19 08:12:09 2021 -0500

    Remove mentions of Java from htdocs/projects/beginner.html

diff --git a/htdocs/projects/beginner.html b/htdocs/projects/beginner.html
index 0a705dbf..3380df40 100644
--- a/htdocs/projects/beginner.html
+++ b/htdocs/projects/beginner.html
@@ -162,7 +162,6 @@ be done with the maintainers of those files.</p>
 targets:</p>
 
 <pre>
-	494K java/parse.y
 	413K combine.c
 	408K dwarf2out.c
 	375K cp/pt.c
@@ -218,9 +217,7 @@ less likely that someone will muck with action code and then forget to
 rebuild the generated parser and check it in.</p>
 
 <p>We also want to minimize the number of helper functions embedded in
-the grammar file.  <code>java/parse.y</code> is a particularly bad
-example, having upwards of 10,000 lines of code after the second
-<code>%%</code>.</p>
+the grammar file.</p>
 </li>
 
 <li>Break up enormous functions.
@@ -849,8 +846,6 @@ include files.  Remember that we already have define_constants.</p>
 
 <ul>
 
-<li>Implement <samp>-std</samp> for the Java front end?</li>
-
 <li>Fix the places where <samp>-std=c89</samp> is not the same thing
 as <samp>-ansi</samp>.</li>
 

-----------------------------------------------------------------------

Summary of changes:
 htdocs/projects/beginner.html | 7 +------
 1 file changed, 1 insertion(+), 6 deletions(-)


hooks/post-receive
-- 
gcc-wwwdocs


                 reply	other threads:[~2021-11-19 13:12 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20211119131228.72EE0385AC0A@sourceware.org \
    --to=egallager@sourceware.org \
    --cc=gcc-cvs-wwwdocs@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).