------- Comment #6 from sebor at roguewave dot com 2008-07-14 15:24 ------- (In reply to comment #4) > ... Is it a reasonable > restriction on users to say "thou shalt not use __is_empty in an expression > that gets mangled"? For example, can the user just use std::is_empty instead?
As a data point, consider that the user may be an author of a third party implementation of the C++ standard library (such as Apache/Rogue Wave or STLport), and they may not be able to use std::is_empty for reasons unique to their project (e.g., policy or otherwise). My preference would be for gcc to avoid imposing restrictions on the use of these helpers to facilitate portability to other compilers such as EDG eccp (the latest 3.10.1 compiles the test case correctly). -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36797
