![](https://secure.gravatar.com/avatar/3a6c2451f75d3309b1252476a8f6a4a6.jpg?s=120&d=mm&r=g)
Duncan Child wrote:
One potential issue is that a units package has to guess whether the user wants to convert a temperature gradient or a temperature: ---snip--- 3) does anyone have input or suggestions regarding the temperature issue?
One thing I'd like to point out is that this is not specific to temperature. Whenever two unit systems have different origins, the unit framework will have to distinguish between differences and positions. (Alternatively, the framework can handle all positional measurements as (X - X_0), and use one general-case transformation.) In general, operators are not unit preserving; it's just that we intuitively expect addition/subtraction to be better behaved than multiplication. Off the top of my head, time measurement also suffers this problem. I'm sure there are others (although they're probably obscure). -Peter