[geos-devel] Thread Safe CAPI next steps?

[Paul Ramsey]

Reading through geosTS_c.h,

- The header information hasn't been updated to reflect authorship.
- The version number defines duplicate the info in geos_c.h, and
double the maintenance overhead (there's some number hardcoded there
because of stoopid MSVCC). A shared version header than both files can
include would be better.
- In fact there's gobs of code that is duplicated across both
headers... I really worry about that. This takes "maintaining two
APIs" to unnecessary heights, I feel.
- Can we just drop the _r methods into the same .h file? (This is a
question, not a request, I may be forgetting some aspect of the
original discussion that answers my question.)

P.

On Thu, Dec 11, 2008 at 1:14 PM, Chuck Thibert
<charles.thibert at ingres.com> wrote:
> Hello all,
>
> Just wanted to find out if there is anything more that needs to be done?
>
> I don't want to send this into the aether and then walk away. :) I'd
> love to see this included in the next release version so if there's
> anything I can do to help ensure this....
>
> Thanks,
> Chuck
> _______________________________________________
> geos-devel mailing list
> geos-devel at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/geos-devel
>