public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Paolo Carlini <pcarlini@unitus.it>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c++/7181: foo<n>::bar = foo<n-1>::bar + foo<n-2>::bar evaluates to zero at compile time
Date: Tue, 02 Jul 2002 14:26:00 -0000	[thread overview]
Message-ID: <20020702212616.1423.qmail@sources.redhat.com> (raw)

The following reply was made to PR c++/7181; it has been noted by GNATS.

From: Paolo Carlini <pcarlini@unitus.it>
To: Nickolai Dobrynin <dobrynin@miller.cs.uwm.edu>
Cc: gcc-gnats@gcc.gnu.org,  gcc-prs@gcc.gnu.org,  dobrynin@bigfoot.com, 
 gcc-bugs@gcc.gnu.org
Subject: Re: c++/7181: foo<n>::bar = foo<n-1>::bar + foo<n-2>::bar evaluates
 to zero at compile time
Date: Tue, 02 Jul 2002 23:17:19 +0200

 Nickolai Dobrynin wrote:
 
 >I just think of it as being totally counter intuitive that the same nifty
 >feature is not valid (is NO LONGER valid, would be a better way to say it)
 >on non-constant initializers.
 >
 >So, would indeed this be possible to restore the behavior of 2.95.x or it
 >would come in conflict with something else? Any opinions on that?
 >
 Nicolai, first thanks for your message from which I have learned much 
 about the issue at hand. On the other hand, I think that Mark's answer 
 stands: if the standard does /not/ prescribe a particular ordering this 
 cannot be considered a bug and, moreover, yourself proved that there is 
 a way (thanks, once more) to do this kind of tricks which does /not/ 
 relies on not well-defined behavior. The latter two points imply that 
 most probably the old behaviour will not be restored very soon ;-)
 
 >PS  Is it a normal behavior that the option -ftemplate-depth-... is no
 >longer needed in order for the example above to compile properly?
 >
 Yes. Currently the default max depth is 500:
 
 2002-01-10  Jakub Jelinek  <jakub@redhat.com>
 
     * decl2.c (max_tinst_depth): Increase default limit to 500.
 
 Ciao,
 Paolo.
 
 


             reply	other threads:[~2002-07-02 21:26 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-02 14:26 Paolo Carlini [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-07-02 13:56 Nickolai Dobrynin
2002-07-02 13:46 Paolo Carlini
2002-07-02 13:36 Paolo Carlini
2002-07-02 13:36 Mark Mitchell
2002-07-02 13:16 Mark Mitchell
2002-07-02 12:56 Nathan Sidwell
2002-07-02 11:31 mmitchel
2002-07-01 15:06 Paolo Carlini
2002-07-01 14:56 Nathan Sidwell
2002-07-01 14:20 paolo

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=20020702212616.1423.qmail@sources.redhat.com \
    --to=pcarlini@unitus.it \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@gcc.gnu.org \
    /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).