5 Apr
2007
5 Apr
'07
4:52 p.m.
I'm actually thinking of including measurement<> with the library itself as a way to provide both physical constants and their associated measurement errors (from CODATA, in particular)
I'm not sure that I'm really keen on this. measurement really doesn't belong in this library.
How about just a wrapper that provides value() and error() accessors and auto conversion to value_type, but no algebra or other functionality? Matthias