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. ca83c13ad6bf0d351220dafa36264ebc7a6b7816
Date: Tue, 23 Nov 2021 23:24:38 +0000 (GMT)	[thread overview]
Message-ID: <20211123232438.25E6E3858012@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  ca83c13ad6bf0d351220dafa36264ebc7a6b7816 (commit)
      from  9c79c04754afc4d35caa77d07d7bad03ccd92a07 (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 ca83c13ad6bf0d351220dafa36264ebc7a6b7816
Author: Eric Gallager <egall@gwmail.gwu.edu>
Date:   Tue Nov 23 18:24:35 2021 -0500

    Remove section on traditional C from htdocs/projects/beginner.html
    
    Traditional C support was already eliminated years ago; that task is complete

diff --git a/htdocs/projects/beginner.html b/htdocs/projects/beginner.html
index 3380df40..4ccb5e12 100644
--- a/htdocs/projects/beginner.html
+++ b/htdocs/projects/beginner.html
@@ -129,23 +129,6 @@ still does generate the warning where it's appropriate), we're happy
 to take those patches too.</p>
 </li>
 
-<li>Eliminate support for compiling with traditional C compilers in
-the language front end subdirectories.
-
-<p>See: <a href="https://gcc.gnu.org/ml/gcc/2002-06/msg00871.html">this
-announcement</a> and the discussion following it which clarifies the
-guidelines.  In addition to the <a
-href="https://gcc.gnu.org/ml/gcc/2002-06/msg00959.html">cleanups listed
-here</a>, one can also consider removing unnecessary casts, such as
-those on the return value of <code>xmalloc</code>, <code>alloca</code>
-and other memory allocation routines, casts on the arguments passed
-e.g. to the <code>mem*</code> functions, casts on <code>0</code>
-e.g. used in assignment, initialization or comparison, etc.  Note
-casts on values passed to stdarg functions or used in <code>~</code>
-mask operations may still be necessary since they ensure type
-width.</p>
-</li>
-
 <li>Find and expunge all the places where one <code>.c</code> file includes
 another.
 

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

Summary of changes:
 htdocs/projects/beginner.html | 17 -----------------
 1 file changed, 17 deletions(-)


hooks/post-receive
-- 
gcc-wwwdocs


                 reply	other threads:[~2021-11-23 23:24 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=20211123232438.25E6E3858012@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).