[gdal-dev] Call for discussion on RFC68: C++11 compilation mode

Kurt Schwehr schwehr at gmail.com
Wed Aug 16 07:37:44 PDT 2017


Thanks for the feedback!   I will fix those things today

On Aug 16, 2017 5:36 AM, "Even Rouault" <even.rouault at spatialys.com> wrote:

> On lundi 14 août 2017 09:44:36 CEST Kurt Schwehr wrote:
>
> > Hi all,
>
> >
>
> > This is a call for discussion on RFC68 to set C++11 to be the minimum C++
>
> > language version for GDAL trunk. I've drafted the RFC based on work by
>
> > Mateusz.
>
> >
>
> > https://trac.osgeo.org/gdal/wiki/rfc68_cplusplus11
>
> >
>
> > There was initial discussions back in January of this year:
>
> >
>
> > https://lists.osgeo.org/pipermail/gdal-dev/2017-
> January/thread.html#45786
>
> >
>
>
>
> Kurt,
>
>
>
> There's one aspect that doesn't appear clearly to me in the RFC text,
> which is requirements for user C++ code using the GDAL C++ API. I presume
> that external code will also have to be compiled in C++11 mode too (because
> of nullptr or override keywords appearing in headers like gcore/gdal_priv.h
> for example). Would probably be worth making that explicit (perhaps in
> "Backward compatibility" paragraph)
>
>
>
> Editorial remarks:
>
> * the reference to "Move OTB to C++14" is after "There are a few related
> past RFCs that have never been adopted but strongly relate to RFC 68", but
> OTB C++14 has been adopted as far as I can see
>
> * the reference to CMake in "If accepted, currently available build
> configurations (Autotools, CMake, NMake)" doesn't apply for GDAL. Regarding
> nmake impacts, there won't be much, apart perhaps removing references to
> MSVC versions older than the new minimum one that will be supported.
>
>
>
> Even
>
>
>
>
>
> --
>
> Spatialys - Geospatial professional services
>
> http://www.spatialys.com
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/gdal-dev/attachments/20170816/9c75e72d/attachment-0001.html>


More information about the gdal-dev mailing list