[Proj] PROJ 5.0.0RC2

[Sebastiaan Couwenberg]

On 02/07/2018 10:07 PM, Kristian Evers wrote:
> Please test and report any problems you may find. Either here or on GitHub. In the unlikely case no issues are discovered I will push the final release two weeks from now.

Is there still room before the final release for API changes?

I'm currently rebuilding all Debian packages that depend on proj, and
this has uncovered some issues in Perl packages: Geo::Proj4 & PDL. They
both include projects.h which contains a UV typedef that conflicts with
a Perl header that contains a UV typedef too.

The related issues are:

 * Geo::Proj4
   https://github.com/markov2/perl5-Geo-Proj4/issues/1
 * PDL
   https://sourceforge.net/p/pdl/bugs/444/

The Geo::Proj4 issues describes (one of) the reasons to include
projects.h instead of relying on the public APIs:

"
 Looking back at the code, my memory tells me that it only has to do
 with being able to get names defined in the library:

  struct PJ_LIST pj_get_list_ref()
  struct PJ_ELLPS pj_get_ellps_ref()
  struct PJ_UNITS pj_get_units_ref()
  struct PJ_DATUM pj_get_datums_ref()

 Access to these tables is very useful to be able to give some help to
 the users. For instance, to create option menus in graphical
 applications. I have no idea whether anyone is using it for real.

 I see that PDL::GIS::Proj also does this:

  my @a = split(/\n/, `echo | proj -v $params`);

 to get some info.
"

What options are there to accommodate the needs of these Perl project in
their use of proj?

Kind Regards,

Bas