From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28549 invoked by alias); 29 Apr 2004 07:53:43 -0000 Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org Received: (qmail 28522 invoked from network); 29 Apr 2004 07:53:42 -0000 Received: from unknown (HELO rocklinux-consulting.de) (212.202.41.96) by sources.redhat.com with SMTP; 29 Apr 2004 07:53:42 -0000 Received: from localhost.localnet ([127.0.0.1] helo=localhost) by rocklinux-consulting.de with esmtp (Exim 4.22) id 1BJ6MX-0008SQ-7s; Thu, 29 Apr 2004 07:53:41 +0000 Date: Thu, 29 Apr 2004 11:45:00 -0000 Message-Id: <20040429.095341.607969633.rene@rocklinux-consulting.de> To: VEKSLER@il.ibm.com Cc: gcc@gcc.gnu.org, valentin@rocklinux-consulting.de Subject: Re: GCC 3.4.0 and template type resolution bug (no) From: Rene Rebe In-Reply-To: References: <20040429.081229.846948283.rene@rocklinux-consulting.de> Mime-Version: 1.0 Content-Type: Text/Plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-Spam-Score: 0.0 (/) X-Spam-Report: Spam detection software, running on the system "heap.localnet", has identified this incoming email as possible spam. The original message has been attached to this so you can view it (if it isn't spam) or block similar future email. If you have any questions, see the administrator of that system for details. Content preview: Hi, thanks for the quick answer. Indeed I have read the release notes - some days ago - and must have overread some lines. On: Thu, 29 Apr 2004 09:23:23 +0300, Michael Veksler wrote: > gcc-3.4 is correct (gcc-3.2 was buggy). Please read gcc-3.4 release notes. > > You should use this->m_info, otherwise the compiler will look for m_info > outside your classes, [...] Content analysis details: (0.0 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- X-SW-Source: 2004-04/txt/msg01367.txt.bz2 Hi, thanks for the quick answer. Indeed I have read the release notes - some days ago - and must have overread some lines. On: Thu, 29 Apr 2004 09:23:23 +0300, Michael Veksler wrote: > gcc-3.4 is correct (gcc-3.2 was buggy). Please read gcc-3.4 release notes. >=20 > You should use this->m_info, otherwise the compiler will look for m_info= =20 > outside your classes, I find this behaviour a bit counter-intuitive. In which section is it enforced by the ANSI standard? Sincerely yours, Ren=E9 Rebe - ROCK Linux stable release maintainer --=20=20 Ren=E9 Rebe - Europe/Germany/Berlin rene@rocklinux.org rene@rocklinux-consulting.de http://www.rocklinux.org http://www.rocklinux-consulting.de