Changed explanation of which value should be greater for maximum efficiency.

This commit is contained in:
Edward Diener
2014-12-05 00:16:11 -05:00
parent 3760758d4e
commit e1ade3ea3b
4 changed files with 4 additions and 4 deletions

View File

@ -34,7 +34,7 @@
It is more efficient, however, to use <b>BOOST_PP_ADD_D</b> in such a situation. It is more efficient, however, to use <b>BOOST_PP_ADD_D</b> in such a situation.
</div> </div>
<div> <div>
This macro is the most efficient when <i>x</i> is less than or equal to <i>y</i>.&nbsp; This macro is the most efficient when <i>x</i> is greater than or equal to <i>y</i>.&nbsp;
However, the efficiency gain is not worth actually comparing the two arguments prior to invocation.&nbsp; However, the efficiency gain is not worth actually comparing the two arguments prior to invocation.&nbsp;
In other words, <i>x</i> should be the addend that is <i>most likely</i> to be the largest of the two operands. In other words, <i>x</i> should be the addend that is <i>most likely</i> to be the largest of the two operands.
</div> </div>

View File

@ -34,7 +34,7 @@
If the sum of <i>x</i> and <i>y</i> is greater than <b>BOOST_PP_LIMIT_MAG</b>, the result is saturated to <b>BOOST_PP_LIMIT_MAG</b>. If the sum of <i>x</i> and <i>y</i> is greater than <b>BOOST_PP_LIMIT_MAG</b>, the result is saturated to <b>BOOST_PP_LIMIT_MAG</b>.
</div> </div>
<div> <div>
This macro is the most efficient when <i>x</i> is less than or equal to <i>y</i>.&nbsp; This macro is the most efficient when <i>x</i> is greater than or equal to <i>y</i>.&nbsp;
However, the efficiency gain is not worth actually comparing the two arguments prior to invocation.&nbsp; However, the efficiency gain is not worth actually comparing the two arguments prior to invocation.&nbsp;
In other words, <i>x</i> should be the addend that is <i>most likely</i> to be the largest of the two operands. In other words, <i>x</i> should be the addend that is <i>most likely</i> to be the largest of the two operands.
</div> </div>

View File

@ -34,7 +34,7 @@
It is more efficient, however, to use <b>BOOST_PP_MUL_D</b> in such a situation. It is more efficient, however, to use <b>BOOST_PP_MUL_D</b> in such a situation.
</div> </div>
<div> <div>
This macro is the most efficient when <i>x</i> is less than or equal to <i>y</i>.&nbsp; This macro is the most efficient when <i>x</i> is greater than or equal to <i>y</i>.&nbsp;
However, the efficiency gain is not worth actually comparing the two arguments prior to invocation.&nbsp; However, the efficiency gain is not worth actually comparing the two arguments prior to invocation.&nbsp;
In other words, <i>x</i> should be the value that is <i>most likely</i> to be the largest of the two operands. In other words, <i>x</i> should be the value that is <i>most likely</i> to be the largest of the two operands.
</div> </div>

View File

@ -34,7 +34,7 @@
If the product of <i>x</i> and <i>y</i> is greater than <b>BOOST_PP_LIMIT_MAG</b>, the result is saturated to <b>BOOST_PP_LIMIT_MAG</b>. If the product of <i>x</i> and <i>y</i> is greater than <b>BOOST_PP_LIMIT_MAG</b>, the result is saturated to <b>BOOST_PP_LIMIT_MAG</b>.
</div> </div>
<div> <div>
This macro is the most efficient when <i>x</i> is less than or equal to <i>y</i>.&nbsp; This macro is the most efficient when <i>x</i> is greater than or equal to <i>y</i>.&nbsp;
However, the efficiency gain is not worth actually comparing the two arguments prior to invocation.&nbsp; However, the efficiency gain is not worth actually comparing the two arguments prior to invocation.&nbsp;
In other words, <i>x</i> should be the value that is <i>most likely</i> to be the largest of the two operands. In other words, <i>x</i> should be the value that is <i>most likely</i> to be the largest of the two operands.
</div> </div>