Hi Alex. Le mar. 20 avr. 2021 à 11:17, Alex Herbert <alex.d.herb...@gmail.com> a écrit : > > [...]
I'm a bit lost in all these bits... ;-) > Any opinions on how changing LinearComination may affect Geometry? Either > we clean up the implementation to use the fast dot2s algorithm with correct > support for splitting 53-bit mantissas, or switch to the extended precision > version. But I do not think we should leave it as the current > implementation which has disadvantages against either of the alternatives. What is your suggestion? My impression is that [Geometry] emphasizes accuracy over ultimate speed (as opposed to libraries used for real-time rendering, I guess). However, could it be possible to leave this as a user's decision? Quoting from Matt's tutorial: ---CUT--- Typically, users of Commons Geometry will construct a single instance of this type for use by multiple objects throughout an entire operation, or even application. Since we don't want our class to assume such a heavy responsibility, we will simply accept a DoublePrecisionContext in the constructor. ---CUT--- Would it be conceivable that the choice of the implementation activated by a call to the "LinearCombination" facility is also encapsulated in the "DoublePrecisionContext"? Regards, Gilles --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
