public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Rene Rebe <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)
Date: Thu, 29 Apr 2004 11:45:00 -0000	[thread overview]
Message-ID: <20040429.095341.607969633.rene@rocklinux-consulting.de> (raw)
In-Reply-To: <OFB34D96D5.F16E9906-ONC2256E85.0022E35B-C2256E85.002345E1@il.ibm.com>

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 <VEKSLER@il.ibm.com> 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,

I find this behaviour a bit counter-intuitive. In which section is it
enforced by the ANSI standard?

Sincerely yours,
  René Rebe
    - ROCK Linux stable release maintainer

--  
René Rebe - Europe/Germany/Berlin
  rene@rocklinux.org rene@rocklinux-consulting.de
http://www.rocklinux.org http://www.rocklinux-consulting.de

  reply	other threads:[~2004-04-29  7:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-29  7:53 GCC 3.4.0 and template type resolution bug Rene Rebe
2004-04-29  8:04 ` GCC 3.4.0 and template type resolution bug (no) Michael Veksler
2004-04-29 11:45   ` Rene Rebe [this message]
2004-04-29 12:15     ` GCC 3.4.0 and template type resolution bug (OT) Michael Veksler
2004-04-29 12:19     ` GCC 3.4.0 and template type resolution bug (no) Giovanni Bajo
2004-04-29  9:08 ` GCC 3.4.0 and template type resolution bug Vladimir Prus

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20040429.095341.607969633.rene@rocklinux-consulting.de \
    --to=rene@rocklinux-consulting.de \
    --cc=VEKSLER@il.ibm.com \
    --cc=gcc@gcc.gnu.org \
    --cc=valentin@rocklinux-consulting.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).