Opened 17 years ago

Last modified 7 years ago

#147 closed defect (fixed)

GEOSCoordSeq_setX also sets y as a side-effect — at Version 3

Reported by: sgillies@… Owned by: mateusz@…
Priority: major Milestone:
Component: C-API Version: 2.2.3
Severity: Significant Keywords: imported, phpbugtracker
Cc:

Description (last modified by mloskot)

The GEOSCoordSeq_setY function does *not* have an effect on x.

I am seeing this with point (size=1) coordinate sequences. I have not yet tested other sequences.

Example code (using Python ctypes, which is pretty much exactly the same as programming in C): 

cs = lgeos.GEOSCoordSeq_create(1, ndim)
# Setting X appears to clobber Y. Watch how the doctest above
# fails.
lgeos.GEOSCoordSeq_setY(cs, 0, dy)
lgeos.GEOSCoordSeq_setX(cs, 0, dx)

Change History (3)

comment:1 by mateusz@…, 17 years ago 

This report seems to be a duplicate of #133

comment:2 by mateusz@…, 17 years ago

Resolution: none → fixed 
The bug #133 was fixed in 2006-12-04, by Sandro, so the issue reported here should be fixed too.

All versions from 3.0.0rc3 should include the fix.

comment:3 by mloskot, 17 years ago

Cc: mloskot added
Description: modified (diff)
Note: See TracTickets for help on using tickets.