feedc0de/boost_config
1
0
Fork 0
forked from boostorg/config
Code Pull Requests Activity

Require a compiler which does not need BOOST_NO_EXPLICIT_FUNCTION_TEMPLATE_ARGUMENTS

Browse Source 
This was defined independent of the compiler version. It is not known
if this is a true limitation of the digital mars compiler in all
versions, or a bug in this header.

(from Stephen Kelly)

Daniel James: I checked the latest version of digital mars. It mostly supports
explicit function template arguments, apart when a function is overloaded for
type and value template arguments, which causes the config test to fail.  So in
most cases the macro isn't needed.

[SVN r85273]
This commit is contained in:
Daniel James
2013-08-10 12:42:22 +00:00
parent 637cd1e6db
commit ffee60eade
1 changed files with 0 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

1
include/boost/config/compiler/digitalmars.hpp
View File

@ -12,7 +12,6 @@
#define BOOST_HAS_PRAGMA_ONCE #define BOOST_HAS_PRAGMA_ONCE
#if !defined(BOOST_STRICT_CONFIG) #if !defined(BOOST_STRICT_CONFIG)
#define BOOST_NO_EXPLICIT_FUNCTION_TEMPLATE_ARGUMENTS
#define BOOST_NO_MEMBER_TEMPLATE_FRIENDS #define BOOST_NO_MEMBER_TEMPLATE_FRIENDS
#define BOOST_NO_OPERATORS_IN_NAMESPACE #define BOOST_NO_OPERATORS_IN_NAMESPACE
#define BOOST_NO_UNREACHABLE_RETURN_DETECTION #define BOOST_NO_UNREACHABLE_RETURN_DETECTION