Yeah, I didn't know about this pragma directive at all. A simple summary about it is here (including disclaimers on use).
https://stackoverflow.com/questions/10261382/why-would-one-use-include-next-in-a-project On Mon, Jun 24, 2024 at 1:20 PM Greg Troxel via gdal-dev < gdal-dev@lists.osgeo.org> wrote: > Scott via gdal-dev <gdal-dev@lists.osgeo.org> writes: > > > #include_next is part of the c++ version 12. You can find it's usage > > here on debian 12: > > > > /usr/include/c++/12/cstdlib, line 75 > > I think that's gcc 12, not C++12 which is not a thing :-) > > It being used in an internal header supplied by the compiler is one > thing. I do not understand how an include of stdlib in a user program > can do that sensibly. It's supposed to mean that only things in the > include path after this file that was found, are to be searched. > That's very tricky and requires assumptions/checks about the include > order, and cmake does not seem to guarantee a lot in that department. > > _______________________________________________ > gdal-dev mailing list > gdal-dev@lists.osgeo.org > https://lists.osgeo.org/mailman/listinfo/gdal-dev >
_______________________________________________ gdal-dev mailing list gdal-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/gdal-dev
