[postgis-tickets] [PostGIS] #3181: Output POINT EMPTY in WKB using NaN as coordinate values

[PostGIS]

#3181: Output POINT EMPTY in WKB using NaN as coordinate values
--------------------------+---------------------------
  Reporter:  pramsey      |      Owner:  pramsey
      Type:  enhancement  |     Status:  reopened
  Priority:  high         |  Milestone:  PostGIS 2.2.2
 Component:  postgis      |    Version:  trunk
Resolution:               |   Keywords:
--------------------------+---------------------------

Comment (by pramsey):

 Rather than using a dynamic NAN as we do now (using a #defined NAN or a
 calculated 0/0 NAN) what if we used an IEEE NAN all the time, just
 hardcode the bytes? It would then be portable. For weirdo platforms it
 might overlap a single legitimate value so we'd be taking a 1 in HUGE
 chance of collision, but I'd accept those terms.

--
Ticket URL: <https://trac.osgeo.org/postgis/ticket/3181#comment:5>
PostGIS <http://trac.osgeo.org/postgis/>
The PostGIS Trac is used for bug, enhancement & task tracking, a user and developer wiki, and a view into the subversion code repository of PostGIS project.