From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9517 invoked by alias); 17 Mar 2004 10:24:43 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Received: (qmail 9500 invoked by alias); 17 Mar 2004 10:24:41 -0000 Date: Wed, 17 Mar 2004 10:24:00 -0000 Message-ID: <20040317102441.9499.qmail@sources.redhat.com> From: "gdr at integrable-solutions dot net" To: gcc-bugs@gcc.gnu.org In-Reply-To: <20040316182307.14608.zack@gcc.gnu.org> References: <20040316182307.14608.zack@gcc.gnu.org> Reply-To: gcc-bugzilla@gcc.gnu.org Subject: [Bug libstdc++/14608] nukes isfinite macro from X-Bugzilla-Reason: CC X-SW-Source: 2004-03/txt/msg02078.txt.bz2 List-Id: ------- Additional Comments From gdr at integrable-solutions dot net 2004-03-17 10:24 ------- Subject: Re: nukes isfinite macro from "zack at codesourcery dot com" writes: | Further comments from the customer ... | | >From: "Zack Weinberg" | >Dennis is not far off. What's happening is that includes | >. includes and then #undefs a bunch of macros | >that a strict reading of C++98 disallows, including "isfinite". | | Strict reading of C++98 would also disallow you undefing user macros | just to make the namespace clean. Strict reading of C++98 requires that the following program compile, if it fails then it is V3 error: #include namespace foo { void isfinite(int) { return 0; } } -- Gaby -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14608