This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug c++/11489] [3.4 Regression] ICE/segfault on legal code


PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11489



------- Additional Comments From neroden at gcc dot gnu dot org  2003-07-12 22:58 -------
Right.  The member 'value' of any type plugged in for C has to be 'static const' in order to be evaluated at instantiation time.  Otherwise it 
requires a specific instance of the type C in order to have a specific value, and the instantiation should fail due to a non-constant expression). 
But that is indeed possible and valid.  :-P  I suppose the true-false status of the types which will be plugged into this is class-specific rather 
than instance-specific.  God only knows what this code is good for, although I'd guess nothing at all.  :-)


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]