-----Original Message----- From: lib2geom-devel-bounces@lists.sourceforge.net [mailto:lib2geom-devel-bounces@lists.sourceforge.net] On Behalf Of Jon A. Cruz Sent: maandag 1 september 2008 20:43 To: Engelen, J.B.C. (Johan) Cc: rwjj@...127...; inkscape-devel@lists.sourceforge.net; lib2geom-devel@lists.sourceforge.net; buliabyak@...400... Subject: Re: [Lib2geom-devel] [Inkscape-devel] Win32 nightly builds don'twork since Aug 16
On Sep 1, 2008, at 5:05 AM, J.B.C.Engelen@...1578... wrote:
I disagree. In the case of paths, the current curve's final point is
exactly the same data as the next curve's initial point. 2geom has this
built-in redundancy in path data because it simplifies things a lot. But
it is important to maintain this data duplication. Therefore, these
points should be exactly (binary) equivalent.
Yes, but the main problem with floating point values is that depending on the rounding involved on calculations to get to some value, things may be equivalent but not an exact match for all bits.
Also keep in mind that precision might vary from platform to platform.
The idea is to get all calculations exactly equal for the initial and final points. So this should not be a problem. If the calculations are not exactly equal, then at the end of the calculation something should be added such that it mimics the "standard" calculation for initial and final points.