Bugs and Limitations

Please report any bugs encountered or limitations experienced to the author.

Here are some evident shortcomings:

1. Auto-expansion of Composed units is disabled in versions up to 1.2.2 due to excessive compilation times.
   
   
2. Intermediate values (named objects of a `type' defined only by its dimension) have not been implemented.
   
   
3. There are no modulo operators (%, and %=).
   
   
4. When copy constructing a target quantity from another one (source), conversion or promotion of the values in the source quantity into the type of the target quantity is not considered. Thus, copy construction is only possible for objects of the same storage type. The same is true for assignment and the += and -= operators. (this is being resolved presently)
   
   
5. There are some incompatibility problems with gcc compiler versions. For more details, see here.
   
   
6. Presently, there is a compatibility problem between the use of Quantities with boost library versions 1.34.x and 1.35.x.
   
   
7. Up to version 1.2.1 only a single UniqueConstant can be derived from a base quantity. This is currently being expanded.
   
   
8. In composed unit symbols, numerator and/or denominator components of the exponent being 0 are correctly parsed although they do not make sense.
   
   
9. In numerical comparison operators, in particular the equality operator (==), the problems of floating point arithmetics are not taken into account. For more information on this issue, see the following links
   • Comparing floating point numbers by Bruce Dawson
   • Comparing Floats: How to Determine if Floating Quantities Are Close Enough Once a Tolerance Has Been Reached by Alberto Squassabia
   • Floating-point comparison algorithms
   • Why doesn't my floating-point comparison work?
   
   
   

back to Quantities start page