[gdal-dev] GDAL trunk is now open for/requires C++11

[Kurt Schwehr]

Thanks Even for driving this to completion!

To follow up, the RFC's list of core changes are pretty limited:

- Change configure.ac to remove with_cpp11 flag, always use C++11, and fail
if AX_CXX_COMPILE_STDCXX_11 does not find C++11
- Remove @CXX11_SUPPORT@ in GDALmake.opt.in and anywhere else it occurs
- Remove continuous build targets that do not support C++11 from Travis-CI
and AppVeyor?
- Remove #if HAVE_CXX11 and leave only the C++11 code
- find . -name \*.h -o -name \*.cpp | xargs egrep 'HAVE_CXX11'
- CPL_STATIC_ASSERT -> static_assert
- NULL -> nullptr (Only for C++ code)
- CPL_OVERRIDE -> override and remove redundant virtual
- MAX or -max() -> std::numeric_limits<T>::lowest()

 It would be worthwhile to (even if only briefly) discuss the use each new
feature before starting to committing changes.  That will help us add to a
GDAL style guide over time.

On Fri, Dec 8, 2017 at 8:42 AM, Even Rouault <even.rouault at spatialys.com>
wrote:

> Hi,
>
>
>
> I've just committed in trunk the changes, initiated by Kurt, needed to
> enforce the C++11 build requirement
>
> ( https://trac.osgeo.org/gdal/wiki/rfc68_cplusplus11 )
>
>
>
> Please have a close look at https://travis-ci.org/OSGeo/gdal/builds and
> https://ci.appveyor.com/project/OSGeo/gdal when using new C++11 features.
>
>
>
> I think it would be good if we could restrict ourselves for now to things
> that VS 2013 can compile. See
>
> https://msdn.microsoft.com/en-us/library/hh567368.aspx
>
>
>
> Even
>
>
>
> --
>
> Spatialys - Geospatial professional services
>
> http://www.spatialys.com
>
> _______________________________________________
> gdal-dev mailing list
> gdal-dev at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/gdal-dev
>



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