Even Rouault <even.roua...@spatialys.com> writes:

>> Would you expect a C++ ABI change every release? 
>
> Except for bugfixes releases, in practice yes for the yearly "feature" 
> release 
> ("feature" meaning here a change of major or minor in the "GDAL 
> major.minor.micro" scheme), as adding a new capability / virtual method, or a 
> new optional parmeter, etc... changes the C++ ABI.

This seems to be the collision between C ABI stability and C++ ABIs that
I expected.  I think that argues for separating them; things in C++ seem
to essentially have to rebuild on most changes, where C isn't like that.

(I tend to look after gdal in pkgsrc, but I haven't run into this yet.)

Attachment: signature.asc
Description: PGP signature

_______________________________________________
gdal-dev mailing list
gdal-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/gdal-dev

Reply via email to