This is the mail archive of the libstdc++@gcc.gnu.org mailing list for the libstdc++ 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]

Re: Keep the macro "complex" in C++03

From: Benjamin De Kosnik <bkoz at redhat dot com>
To: libstdc++ at gcc dot gnu dot org
Date: Thu, 14 Feb 2013 11:42:25 -0800
Subject: Re: Keep the macro "complex" in C++03
References: <alpine.DEB.2.02.1302132036420.20716@stedding.saclay.inria.fr> <81a8124e-2e54-4ebd-97e2-c2808764ed92@email.android.com>

> Patch is Ok, thanks. You may want to remove the test variable: it
> serves no purpose in a dg-do compile testcase with no VERIFYs in it.

OT, but I cannot resist.

Continued use of VERIFY is VERY inane.

1) static_assert in C++11 is much better for do-compile

2) just throwing an exception with details that are automagically
logged via verbose_terminate is much better for do-run

I've switched over to these two mechanisms. 

-benjamin

References:
- Keep the macro "complex" in C++03
  - From: Marc Glisse
- Re: Keep the macro "complex" in C++03
  - From: Paolo Carlini

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