[Proj] Coming releases of PROJ.4

[Even Rouault]

> It was also why I suggested to keep a maintenance version based on 4.9.4 for
> a few years. So developers have time to absorb the changes in their own
> time.

I think that it is important to have at some point a release that has both functional proj_api.h 
and proj.h so that it can serve as a migration basis. If a project doesn't want to be compatible 
of both API and migrate directly to the new API, it must be able to rely on the new API in a 
release. So maintainance versions of 4.9 will have to fix potential issues in proj.h and related 
implementation. I'm also thinking to Linux distributions that will be able to ship only a single 
proj version and will perhaps have packages that still use the old API while others have 
already migrated.

I'm thinking as a potential test for the new API to use the code sprint at FOSS4G-Europe to 
try to make GDAL use the new API.

> I think it should be possible to remove the dependency of proj_api.h in
> proj.h. Perhaps by putting the parts that are dependant on proj_api.h in a
> proj_internal.h as suggested in your GitHub issue?

Yes, proj.h should be as clean as possible. And I wouldn't mind if there are duplicated 
declarations in proj.h and proj_api.h. Actually I think both should be mutually exclusive and 
self-contained. It makes little sense to include both in the same compilation unit. Of course 
that will require some care of not putting conflicting declarations for the same function...

-- 
Spatialys - Geospatial professional services
http://www.spatialys.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.maptools.org/pipermail/proj/attachments/20170622/b82ff8eb/attachment-0001.htm