From: steven_at_[hidden]
Date: 2008-05-31 18:05:41
Author: steven_watanabe
Date: 2008-05-31 18:05:41 EDT (Sat, 31 May 2008)
New Revision: 45994
URL: http://svn.boost.org/trac/boost/changeset/45994
Log:
Improvments to conversion documentation
Text files modified:
sandbox/units/libs/units/doc/units.qbk | 10 +++-------
1 files changed, 3 insertions(+), 7 deletions(-)
Modified: sandbox/units/libs/units/doc/units.qbk
==============================================================================
--- sandbox/units/libs/units/doc/units.qbk (original)
+++ sandbox/units/libs/units/doc/units.qbk 2008-05-31 18:05:41 EDT (Sat, 31 May 2008)
@@ -427,6 +427,9 @@
Since the SI unit of length is the meter, these two
definitions have exactly the same effect.
+If these conversions have been defined, then converting between
+scaled forms of these units will automatically work.
+
The macro [___BOOST_UNITS_DEFAULT_CONVERSION] specifies a conversion
that will be applied to a base unit when no direct conversion is
possible. This can be used to make arbitray conversion work
@@ -438,13 +441,6 @@
// make conversion to SI the default.
BOOST_UNITS_DEFAULT_CONVERSION(my_unit_tag, SI::force);
-The following are the exact rules for conversions.
-First the implementation attempts to find a direct conversion defined
-with [___BOOST_UNITS_DEFINE_CONVERSION_FACTOR] and its kin. If there is no such
-exact conversion then it will look for a definition of some scaled
-form of the conversion. If that also fails then it will transform
-every [___base_unit] using [___BOOST_UNITS_DEFAULT_CONVERSION] and recurse.
-
[endsect]
[section:Examples Examples]