[gdal-dev] Why is CSLUniquePtr internal?

[Kurt Schwehr]

Since the C style string lists get exposed so often in the API, I am
strongly in favor of exposing it and encouraging its use.

I am of the opinion that modern C++ code should rarely use bare
malloc/free/new/delete and variants of those (doubly strong for the delete
side) .

Anyone have a reason to not expose it?

On Mon, Jan 8, 2018 at 9:15 AM, Even Rouault <even.rouault at spatialys.com>
wrote:

> On lundi 8 janvier 2018 09:08:44 CET Kurt Schwehr wrote:
>
> > Even,
>
> >
>
> > In https://trac.osgeo.org/gdal/changeset/41104, you put CSLUniquePtr
>
> > behind GDAL_COMPILATION. Can you explain why? I would like to use it in
>
> > some of my code rather than the usual MakeCleanup with CPLDestroy that I
>
> > usually do.
>
>
>
> I didn't really feel that needed to be part of the API. I don't have a
> strong opinion on this though
>
>
>
> Even
>
>
>
> --
>
> Spatialys - Geospatial professional services
>
> http://www.spatialys.com
>



-- 
--
http://schwehr.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/gdal-dev/attachments/20180108/48d71895/attachment.html>