forked from boostorg/type_traits
Updated to use BOOST_NO_IS_ABSTRACT.
[SVN r26424]
This commit is contained in:
1 parent
bbbd77d3e9
commit
22d2d9b641
2 files changed
+14
-4
No files matched your search
+10
-3
@@ -358,9 +358,16 @@
|
||||
<TD vAlign="top" bgColor="#c0c0c0"><code>::boost::is_abstract<T>::value</code></TD>
|
||||
<TD vAlign="top" bgColor="#c0c0c0">Evaluates true only if T is abstract class.</TD>
|
||||
<TD vAlign="top" bgColor="#c0c0c0">10.3</TD>
|
||||
<TD vAlign="top" bgColor="#c0c0c0">Compiler must support DR337 (as Jan 2004: GCC
|
||||
3.4,<BR>
|
||||
VC++ 7.1, Intel C++ 7, Comeau 4.3.2).</TD>
|
||||
<TD vAlign="top" bgColor="#c0c0c0">
|
||||
<P>Compiler must support DR337 (as Jan 2004: GCC 3.4, VC++ 7.1, Intel C++ 7, and
|
||||
Comeau 4.3.2).</P>
|
||||
<P>Otherwise produces the same value as is_polymorphic<T>::value; this is
|
||||
the "safe fallback position" for which polymorphic types are
|
||||
always regarded as potentially abstract.</P>
|
||||
<P>The macro BOOST_NO_IS_ABSTRACT is used to signify that the implemention is
|
||||
buggy, users should check for this in their own code if the "safe fallback" is
|
||||
not suitable for their particular use-case.</P>
|
||||
</TD>
|
||||
<TD vAlign="top" width="5%"></TD>
|
||||
</TR>
|
||||
<tr>
|
||||
|
||||
Reference in new issue
Block a user