[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Emacs-diffs] master b7fa6b1 1/4: Simplify use of FOR_EACH_TAIL

From: Richard Stallman
Subject: Re: [Emacs-diffs] master b7fa6b1 1/4: Simplify use of FOR_EACH_TAIL
Date: Tue, 07 Feb 2017 16:50:07 -0500

[[[ To any NSA and FBI agents reading my email: please consider    ]]]
[[[ whether defending the US Constitution against all enemies,     ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]

  > constraint can be interpreted as meaning (A) when a for-statement 
  > declares an object's name, the name must have storage class auto or 
  > register, or (B) all identifiers declared by a for-statement must name 
  > objects with storage class auto or register. Although I suspect (A) was 
  > intended and that's what GCC does, (B) is also a plausible 
  > interpretation and that's what Clang does. Interpretation (B) disallows 
  > anonymous structs here, as such structs declare member names.

Why should we restrict ourselves to cater to Clang?
That makes no sense for us.

We should write this code the right way, and recommend that
people compile with GCC.  People who want to compile with Clang
can cope in one way or another.

Dr Richard Stallman
President, Free Software Foundation (gnu.org, fsf.org)
Internet Hall-of-Famer (internethalloffame.org)
Skype: No way! See stallman.org/skype.html.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]