why are p#d_same using FP_EQUALS ?

[Sandro Santilli]

Given it's the second time that I stumble upon issues related
to use of FP_EQUALS in the p2d_same and p4d_same functions I'm
wondering why those FP_EQUALS macros were added at all.

Does anyone remember the rationale for that ?

The two cases:
  - https://trac.osgeo.org/postgis/ticket/5698
  - https://trac.osgeo.org/postgis/ticket/5394

In topology I've stopped using the p2d_same method for the
problem using tolerance raises, but this time the problem
was in the ST_Split function itself. Same cause (considering
two almost-but-not-exactly-equal points equal).

Should we stop that ?

--strk; 

  Libre GIS consultant/developer
  https://strk.kbt.io/services.html
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 659 bytes
Desc: not available
URL: <http://lists.osgeo.org/pipermail/postgis-devel/attachments/20240322/34bdee42/attachment.sig>