
Geometry : 
Subject: Re: [geometry] extensions
From: Bruno Lalande (bruno.lalande_at_[hidden])
Date: 20120208 04:40:37
Hi,
Regarding lexical_cast => would probably be better to have that
encapsulated somewhere rather than having the same #ifdef at several places
of the code.
Regarding constants => So we assume that the other compilers will be clever
enough to figure out that it's a constant and make it static? If the TI
compiler is flawed enough not to manage constants as the standard states,
we shouldn't expect all the other compiles to go *beyond* the standard and
make a nonstatic variable static.
Also, Boost.Math already has those constants:
constants/constants.hpp: BOOST_DEFINE_MATH_CONSTANT(pi,
3.141592653589793238462643383279502884197169399375105820974944,
59230781640628620899862803482534211706798214808651328230664709384460955058223172535940812848111745028410270193852110555964462294895493038196,
0)
constants/constants.hpp: BOOST_DEFINE_MATH_CONSTANT(two_pi,
6.2831853071795864769252867665590057683943388015061, 0, 0)
If we can't reuse them for some reason (to be checked), we can at least see
what this BOOST_DEFINE_MATH_CONSTANT is about, it's purpose might be to
solve our problem, precisely.
Sorry these are just quick ideas, I don't have the time to dig more right
now...
Regards
Bruno
Geometry list run by mateusz at loskot.net