Re: [gcc-announce-owner@gcc.gnu.org] Returned post for gcc-announce@gcc.gnu.org

[Jason Molenda <jason-swarelist@molenda.com>]

The moderators are law@redhat.com and mark@codesourcery.com--one
of them apparently rejected the post (or made a mistake while
trying to approve it).

On Thu, Feb 06, 2003 at 01:20:42PM -0800, Zack Weinberg wrote:
> 
> How do I get this posted to gcc-announce?
> 
> zw
> 

> Date: 6 Feb 2003 21:01:11 -0000
> From: gcc-announce-owner@gcc.gnu.org
> To: zack@codesourcery.com
> Subject: Returned post for gcc-announce@gcc.gnu.org
> 
> Hi! This is the ezmlm program. I'm managing the
> gcc-announce@gcc.gnu.org mailing list.
> 
> I'm sorry, your message (enclosed) was not accepted by the moderator.
> If the moderator has made any comments, they are shown below.

> To: gcc@gcc.gnu.org, gcc-announce@gcc.gnu.org
> Subject: #import, #pragma once to be removed in 3.4
> From: Zack Weinberg <zack@codesourcery.com>
> Date: Thu, 06 Feb 2003 12:49:19 -0800
> 
> 
> So we had a discussion of the problems that PCH poses for #import,
> which expanded to a discussion of the problems of #import and
> #pragma once generally, which then pretty much wound down without any
> middle ground being found between 'there must be some way to fix it'
> and 'no, sorry, there isn't'.  I think that an executive decision is
> required at this point, which falls to me as cpplib maintainer.
> 
> Accordingly: #import and #pragma once will be removed from FSF GCC in
> 3.4.  I will shortly send a patch to gcc-patches to implement that.
> 
> I have heard the concerns of the people who have problems with the
> remaining mechanism for idempotent #include, i.e. wrapper #ifndefs.
> I have a solution in mind, but I would first like to determine how
> widespread these problems are.  Please reply to this message
> (do NOT cc: gcc-announce) if you have experienced problems with
> collisions between macro names used in wrapper #ifndefs, or any other
> technical problem with this mechanism.  Please also advise if you
> could not work around the problem by editing the offending headers.
> 
> zw