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
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
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.
Thanks,
-kurt
___
g
FYI
-- Forwarded message --
From: Margherita Di Leo
Date: Mon, Jan 8, 2018 at 12:13 PM
Subject: Call for mentors for Google Summer of Code 2018
To: OSGeo Discussions
Cc: "gsoc-adminosgeo.org"
Dear members of the community,
while we're still very busy in Google Code-in, which
Marco De Nadai wrote
> Dear gdal community,
> I'm a new user of gdal and I recently had a problem with precision. I
> tried
> to translate a big GeoTIFF to a smaller one, specifying the extent of the
> window in this way:
Hi,
It seems that you asked the same question in
https://gis.stackexchange.
