public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Nickolai Dobrynin <dobrynin@miller.cs.uwm.edu> 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 13:56:00 -0000 [thread overview] Message-ID: <20020702205613.24309.qmail@sources.redhat.com> (raw) The following reply was made to PR c++/7181; it has been noted by GNATS. From: Nickolai Dobrynin <dobrynin@miller.cs.uwm.edu> To: Paolo Carlini <pcarlini@unitus.it> Cc: <gcc-gnats@gcc.gnu.org>, <gcc-prs@gcc.gnu.org>, <dobrynin@bigfoot.com>, <gcc-bugs@gcc.gnu.org>, Mark Mitchell <mark@codesourcery.com>, Nathan Sidwell <nathan@codesourcery.com> Subject: Re: c++/7181: foo<n>::bar = foo<n-1>::bar + foo<n-2>::bar evaluates to zero at compile time Date: Tue, 2 Jul 2002 15:52:27 -0500 (CDT) Hello! Actually, the original example from the "Generative Programming" book looked like this: #include <iostream> using namespace std; template<int n> struct Fib { enum { RET = Fib<n-1>::RET + Fib<n-2>::RET }; }; template<> struct Fib<0> { enum { RET = 0 }; }; template<> struct Fib<1> { enum { RET = 1 }; }; void main() { cout << Fib<8>::RET << endl; } -- which, evidently, is not identical to what I was submitting in my original message. After eliminating the "enum hack" (an optional step), i.e. replacing enum with const static int, #include <iostream> using namespace std; template<int n> struct Fib { const static int RET = Fib<n-1>::RET + Fib<n-2>::RET; }; struct Fib<0> { const static int RET = 0; }; struct Fib<1> { const static int RET = 1; }; int main() { cout << Fib<40>::RET << endl; return 0; } this will indeed produce a valid output. 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? Regards, Nickolai PS Is it a normal behavior that the option -ftemplate-depth-... is no longer needed in order for the example above to compile properly? On Tue, 2 Jul 2002, Paolo Carlini wrote: > Hi, > > from a very practical point of view, would be difficult to restore the > behaviour of 2.95.x? Note that Intel and Comeau adopts that "particular" > initialization order and the current "equivalent" one ;-) breaks a whole > body of literature on template metaprogramming... > > Ciao, Paolo. > > http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=7181 > > >
next reply other threads:[~2002-07-02 20:56 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-07-02 13:56 Nickolai Dobrynin [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-07-02 14:26 Paolo Carlini 2002-07-02 13:46 Paolo Carlini 2002-07-02 13:36 Mark Mitchell 2002-07-02 13:36 Paolo Carlini 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=20020702205613.24309.qmail@sources.redhat.com \ --to=dobrynin@miller.cs.uwm.edu \ --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: linkBe 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).