[geos-devel] updating geos 3.5.0 source archive.
mohammedrashadkm at gmail.com
Tue Nov 10 08:37:53 PST 2015
On Tue, Nov 10, 2015 at 12:11 PM, Jürgen E. <jef at norbit.de> wrote:
> Hi Mateusz,
> On Tue, 10. Nov 2015 at 10:50:57 +0100, Mateusz Loskot wrote:
> > > Why not? Other projects have to. I'd prefer to keep the C++ API out
> > > of the picture.
> > If I may, one correction: other projects do NOT have to, but they choose
> > GEOS C++ API is an official API perfectly supported and
> > recommended to use by GEOS users.
> Sure. And as the C-API doesn't cover everything, it's sometimes even
> unavoidable to use the C++ API (or requires to extend the C-API).
> > There is, however, cost involved. That is, GEOS does not promise C++
> > stability, so those who choose GEOS C++ API should be aware they may need
> > to update change their code more frequently.
> Also right - plus that we need to either pick one C++ compiler that works
> everyone (Qt and reverse dependencies currently use 2010 in OSGeo4W - not
> 2012), leave some behind or ship a myriad of different packages to suit
> > So, I don't think it's a good idea to forbid the freedom of GEOS API
> > especially if it is a choice between officially supported APIs.
> I just stated a preference - and asked whether it is feasible to port
> OSSIM to
> the C-API.
According to OSSIM, if GEOS moves away completely from c++ api. i.e. there
is no more c++ api with newer geos release. then okay.
I know GEOS C-API is recommended. but as stated by Mateusz, c++ API is not
forbidden. So ossim uses. the current osgeo4w version of ossim is 1.8.16.
and latest stable release is 1.8.20. The only blocker is geos c++ api. That
is why I asked.
> Jürgen E. Fischer norBIT GmbH Tel.
> Dipl.-Inf. (FH) Rheinstraße 13 Fax.
> Software Engineer D-26506 Norden
> geos-devel mailing list
> geos-devel at lists.osgeo.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the geos-devel