From: Eric Gallager <egall@gwmail.gwu.edu>
To: gcc-patches <gcc-patches@gcc.gnu.org>
Subject: [PATCH][wwwdocs] remove references to java in htdocs/projects/beginner.html
Date: Thu, 18 Nov 2021 20:37:52 -0500 [thread overview]
Message-ID: <CAMfHzOvA35q9qSj_P1oORHi87f-d_kbka=A7VgTE+Wtk8LbMeA@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 716 bytes --]
So, on the wiki page for EasyHacks
<https://gcc.gnu.org/wiki/EasyHacks>, it says: "There is also a
non-wiki list of beginner projects at
http://gcc.gnu.org/projects/beginner.html, however, it is very
outdated and the projects are not that easy." Since I don't have an
account on the wiki (since creating a separate wiki account that's
different from my Bugzilla account would create difficulties for my
password manager), but I do have commit access, I'd find it easier to
just edit the page linked to in wwwdocs instead, so I'm going to start
seeing what I can do to update it. I figured I'd start by removing the
references to Java in it, since Java has been removed. A patch to do
that is attached.
Eric Gallager
[-- Attachment #2: patch-beginner-projects-01.diff --]
[-- Type: application/octet-stream, Size: 1043 bytes --]
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>
next reply other threads:[~2021-11-19 1:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-19 1:37 Eric Gallager [this message]
2021-11-19 6:48 ` Gerald Pfeifer
2021-11-19 13:14 ` Eric Gallager
2021-11-23 23:27 ` [committed][wwwdocs] Remove section on traditional C from htdocs/projects/beginner.html Eric Gallager
2021-11-24 7:11 ` [PATCH][wwwdocs] Update section on enormous source files in htdocs/projects/beginner.html Eric Gallager
2021-12-01 15:14 ` PING " Eric Gallager
2021-12-01 15:54 ` Gerald Pfeifer
2021-12-01 17:26 ` Eric Gallager
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='CAMfHzOvA35q9qSj_P1oORHi87f-d_kbka=A7VgTE+Wtk8LbMeA@mail.gmail.com' \
--to=egall@gwmail.gwu.edu \
--cc=gcc-patches@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).