GEOSCoordSeq_setZ is inconsistent

[hrz@…]

GEOSCoordSeq_setZ doesn't work as expected when it's called *before* either _setX or _setY. I would expect the following code to print z=43.2 but instead it prints z=78.9

    double z = 0;
    coords = GEOSCoordSeq_create(1, 3);

    GEOSCoordSeq_setZ(coords, 0, 43.2);
    GEOSCoordSeq_setX(coords, 0, 12.5);
    GEOSCoordSeq_setY(coords, 0, 78.9);

    GEOSCoordSeq_getZ(coords, 0, &z);
    printf("z=%.1fn", z);

I suppose the other alternative is that _getZ isn't working as expected!

My system is:

$ uname -a
Linux 2.6.18-gentoo-r3 #1 PREEMPT Wed Nov 29 09:26:52 GMT 2006 i686 AMD Athlon(tm) XP 2800+ AuthenticAMD GNU/Linux

and GEOS CAPI 3.0.0rc2-CAPI-1.3.0 with:
$ gcc-config -c
i686-pc-linux-gnu-4.1.1

[strk@…]

Confirmed, it seems that also swapping setX with setY breaks it :-!

[hrz@…]

Works fine for me now, although I haven't tested for swapping setX with setY - only setZ as described in the initial report.

[mateusz@…]

This bug was fixed in 2006-12-04, by Sandro.
All versions from 3.0.0rc3 should include the fix.

[(none)]

Milestone 3.0.0 deleted