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. 4925e512562987e45d2ff7abffc9c6aa527c1240 Date: Wed, 24 Nov 2021 01:17:05 +0000 (GMT) [thread overview] Message-ID: <20211124011705.897313858C2C@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 4925e512562987e45d2ff7abffc9c6aa527c1240 (commit) from 0ec82f74b170295385f3a1f288e5d371fe5469b9 (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 4925e512562987e45d2ff7abffc9c6aa527c1240 Author: Eric Gallager <egall@gwmail.gwu.edu> Date: Tue Nov 23 20:16:54 2021 -0500 htdocs/projects/beginner.html: remove section on files including one another all remaining instances of .c (or .cc) files including one another are intentional, apparently, so that section can just be removed instead. diff --git a/htdocs/projects/beginner.html b/htdocs/projects/beginner.html index 5d055883..589b47c8 100644 --- a/htdocs/projects/beginner.html +++ b/htdocs/projects/beginner.html @@ -129,16 +129,6 @@ still does generate the warning where it's appropriate), we're happy to take those patches too.</p> </li> -<li>Find and expunge all the places where one <code>.c</code> (or -<code>.cc</code>) file includes another. - -<p>In most cases this is just sloppiness, and can easily be converted -to separate compilation of both files, then linking the two objects -together. There may be places where someone is trying to simulate -generic programming through the macro facility. Discuss what should -be done with the maintainers of those files.</p> -</li> - <li>Break up enormous source files. <p>Not terribly hard. Watch out for file-scope globals. Suggested ----------------------------------------------------------------------- Summary of changes: htdocs/projects/beginner.html | 10 ---------- 1 file changed, 10 deletions(-) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2021-11-24 1:17 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=20211124011705.897313858C2C@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: linkBe 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).