mirror of
https://github.com/boostorg/functional.git
synced 2026-01-19 04:12:10 +00:00
509a1a8834
https://svn.boost.org/svn/boost/branches/unordered/trunk ........ r43840 | danieljames | 2008-03-24 17:25:07 +0000 (Mon, 24 Mar 2008) | 1 line Fix a g++ warning. ........ r43844 | danieljames | 2008-03-24 17:56:28 +0000 (Mon, 24 Mar 2008) | 1 line It's a new-ish year. ........ r43885 | danieljames | 2008-03-27 20:36:10 +0000 (Thu, 27 Mar 2008) | 1 line The release script doesn't need to copy images and css - because that's now done in the jamfiles. Also tweak the shell script a tad bit. ........ r43890 | danieljames | 2008-03-27 23:01:40 +0000 (Thu, 27 Mar 2008) | 1 line Starting to add a docbook bibliography. ........ r43894 | danieljames | 2008-03-27 23:24:18 +0000 (Thu, 27 Mar 2008) | 1 line Redeclare 'data' in iterator_base to help compilers which have trouble with accessing the nested typedef. ........ [SVN r43895]
30 lines
1.4 KiB
Plaintext
30 lines
1.4 KiB
Plaintext
|
|
[/ Copyright 2005-2008 Daniel James.
|
|
/ Distributed under the Boost Software License, Version 1.0. (See accompanying
|
|
/ file LICENSE_1_0.txt or copy at http://www.boost.org/LICENSE_1_0.txt) ]
|
|
|
|
[section:disable Disabling The Extensions]
|
|
|
|
While [classref boost::hash]'s extensions are generally useful, you might want
|
|
to turn them of in order to check that your code will work with other
|
|
implementations of TR1. To do this define the macro `BOOST_HASH_NO_EXTENSIONS`.
|
|
When this macro is defined, only the specialisations detailed
|
|
in TR1 will be declared. But, if you later undefine the macro and include
|
|
<[headerref boost/functional/hash.hpp]> then the non-specialised form will be defined
|
|
- activating the extensions.
|
|
|
|
It is strongly recommended that you never undefine the macro - and only define
|
|
it so that it applies to the complete translation unit, either by defining it
|
|
at the beginning of the main source file or, preferably, by using a compiler
|
|
switch or preference. And you really should never define it in header files.
|
|
|
|
If you are writing a library which has code in the header which requires the
|
|
extensions, then the best action is to tell users not to define the macro.
|
|
Their code won't ['require] the macro.
|
|
|
|
Translation units that are compiled with the macro defined will link with units
|
|
that were compiled without it. This feature has been designed to avoid ODR
|
|
violations.
|
|
|
|
[endsect]
|