I recently tested boost::polygon to perform complex Boolean unions of polygonal data with overlapping segments and many intersections to one point. I had to change the default high_precision_type<int>::type to multiprecision::int128_t because it defaults to long double. I wanted to capture 30 bits of an int. I suspect that this code was written back when long double was actually a long double on Windows and not an euphemism for double.
Has anyone encountered a similar issue?
Asked
Active
Viewed 6 times
0
Catriel
- 461
- 3
- 11
-
You changed an IEEE float type to an integral type? Did you get a documented recommendation to do so? "I wanted to capture 30 bits of an int" - what does that mean in context? – sehe Sep 01 '23 at 23:12