From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28276 invoked by alias); 6 Feb 2003 21:20:44 -0000 Mailing-List: contact overseers-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: , Sender: overseers-owner@sources.redhat.com Received: (qmail 28269 invoked from network); 6 Feb 2003 21:20:44 -0000 Received: from unknown (HELO egil.codesourcery.com) (66.92.14.122) by 172.16.49.205 with SMTP; 6 Feb 2003 21:20:44 -0000 Received: from zack by egil.codesourcery.com with local (Exim 3.36 #1 (Debian)) id 18gtRq-00078F-00 for ; Thu, 06 Feb 2003 13:20:42 -0800 To: overseers@sources.redhat.com Subject: [gcc-announce-owner@gcc.gnu.org] Returned post for gcc-announce@gcc.gnu.org From: Zack Weinberg Date: Thu, 06 Feb 2003 21:20:00 -0000 Message-ID: <87ptq5kswl.fsf@egil.codesourcery.com> User-Agent: Gnus/5.090014 (Oort Gnus v0.14) Emacs/21.2 (i386-pc-linux-gnu) MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="=-=-=" X-SW-Source: 2003-q1/txt/msg00266.txt.bz2 --=-=-= Content-length: 48 How do I get this posted to gcc-announce? zw --=-=-= Content-Type: message/rfc822 Content-Disposition: inline Content-length: 2810 Return-Path: Delivered-To: zack@codesourcery.com Received: (qmail 21158 invoked from network); 6 Feb 2003 21:01:41 -0000 Received: from sources.redhat.com (66.187.233.205) by www.codesourcery.com with SMTP; 6 Feb 2003 21:01:41 -0000 Received: (qmail 18147 invoked by alias); 6 Feb 2003 21:01:11 -0000 Mailing-List: contact gcc-announce-help@gcc.gnu.org; run by ezmlm Date: 6 Feb 2003 21:01:11 -0000 Message-ID: <1044565271.18145.ezmlm@gcc.gnu.org> From: gcc-announce-owner@gcc.gnu.org To: zack@codesourcery.com Subject: Returned post for gcc-announce@gcc.gnu.org MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===-=-=" --===-=-= Content-length: 220 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. --===-=-= Content-Type: message/rfc822 Content-length: 1856 Return-Path: Delivered-To: moderator for gcc-announce@gcc.gnu.org Received: (qmail 10554 invoked from network); 6 Feb 2003 20:49:20 -0000 Received: from unknown (HELO egil.codesourcery.com) (66.92.14.122) by 172.16.49.205 with SMTP; 6 Feb 2003 20:49:20 -0000 Received: from zack by egil.codesourcery.com with local (Exim 3.36 #1 (Debian)) id 18gsxT-00076F-00; Thu, 06 Feb 2003 12:49:19 -0800 To: gcc@gcc.gnu.org, gcc-announce@gcc.gnu.org Mail-Followup-To: gcc@gcc.gnu.org Subject: #import, #pragma once to be removed in 3.4 From: Zack Weinberg Date: Thu, 06 Feb 2003 12:49:19 -0800 Message-ID: <87lm0tjfsg.fsf@egil.codesourcery.com> User-Agent: Gnus/5.090014 (Oort Gnus v0.14) Emacs/21.2 (i386-pc-linux-gnu) MIME-Version: 1.0 Content-length: 1077 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 --===-=-=-- --=-=-=--