----- Original Message ----- From: "David Mertens"

Hi David,


Hey Rob -

Every code contribution is important. I don't use PROJ, but I appreciate
*any* work that makes PDL a better tool! However, I'm sure you can
understand Chris's frustration here: he needs to be absolutely sure that
any changes he makes do not break anything in PDL, yet tests were failing,
and he was able to reproduce PROJ test failures on his own machine using
old PROJ libraries. Ergo, revert the PROJ changes and re-release.

Since Chris is in the middle of some nontrivial internals work, and since
Chris is the project maintainer, I think he is justified rolling back to a
previous set of bindings so that he can be confident that nothing breaks in
his work. But once his work has finished (or at least reached a stable
point), we should push forward with your PROJ updates. In the meantime, I
doubt you need the memory mapping code, so holding your own PDL back at
2.4.10_001 would probably work out fine.

I can build 2.4.10_002 (with my patched proj.pd) against proj-4.8.0, proj-4.7.0 and proj-4.6.1. It was proj-4.6.1 that failed for Chris, and I can't reproduce that failure - nor do I know what his failure even looks like. Do I need to build _003 against proj-4.6.1 in order to see the deficiency in my proj.pd ?
Or do I need to go back earlier than 4.6.1 ?
Or do I need to use another OS ?

Now that cpantesters is down (and who knows how long that will last), I can't even see anything there. I wish I had taken a look at cpantesters sooner ... but I can't do much about that, now.

Chris may have been a bit hasty in calling your contribution "broken."
Chris is a nice guy and I'm sure it was out of honest frustration. But too
much hastiness leads to flared tempers, so let's all take a deep breath,
let the "smoke" clear on the memory mapping, and then work on the PROJ
bindings.


I'm sure my demeanour will improve when I can actually get to *see* an error report for _001. (It would also be helpful if said error report also provided the version number of the proj library - but I don't think that can be derived from cpantesters reports.)

In the meantime, I'll just have to try to be patient .... I guess.

Cheers,
Rob


_______________________________________________
Perldl mailing list
[email protected]
http://mailman.jach.hawaii.edu/mailman/listinfo/perldl

Reply via email to