From: [EMAIL PROTECTED]
Even if angle is added as a dimension, to an implementation using an
integer vector, it still wouldn't accommodate any other dimensions
added later, without rewriting the library and unit definitions.
how about having the basic SI dimensions and a couple of extra
From: David Abrahams [EMAIL PROTECTED]
These are my (only slightly informed) opinions. I've heard Walter
Brown talk about angle in this context, which was a big influence.
Terje Slettebø [EMAIL PROTECTED] writes:
Regarding this angle dimension, should it be treated like the other
From: [EMAIL PROTECTED]
we use the int-based template approach for a couple of years now in
our AGV controller software. We actually sometimes reach the stage that
it works when succesfully compiled and linked. Since our control software
is physics throughout (field of robotics), the type
Terje Slettebø [EMAIL PROTECTED] writes:
From: David Abrahams [EMAIL PROTECTED]
These are my (only slightly informed) opinions. I've heard Walter
Brown talk about angle in this context, which was a big influence.
Terje Slettebø [EMAIL PROTECTED] writes:
Regarding this angle dimension,
From: [EMAIL PROTECTED]
we use the int-based template approach for a couple of years now in
our AGV controller software. We actually sometimes reach the stage
that it works when succesfully compiled and linked. Since our control
software is physics throughout (field of robotics), the type
I wrote Quantity library some time ago and wonder whether it may get added
into Conversion library. If anyone gets interested I will Boostify and
submit it.
Quantity library is used to get safe conversions between different physical
units (like between Celsius and Farhernheit degrees). Instead
