[gdal-dev] Breaking API Change

[Andrew Bell]

Andrew Bell
andrew.bell.ia at gmail.com

On Fri, Jan 30, 2026, 3:32 PM Daniel Baston <dbaston at gmail.com> wrote:

> Andrew,
>
> I don't think any ship has sailed -- 3.13 will not be released for several
> months.
>

I just meant that the API has been consistent for like 30 years.

>
> Is there a situation where the change to client code is more involved than
> changing "char**" to "CSLConstList" ?
>

Yep. But it still requires users to change their code for little to no
benefit. My general feeling is that you need a darn good reason to require
users to change their existing code, but others are welcome to disagree.

A different interface for this kind of thing would be nice. Perhaps
something better can be done and these functions can be deprecated? I'm
sure there are various options.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/gdal-dev/attachments/20260130/62942792/attachment-0001.htm>