Rob/All-
I want to apologize for the quick reversion of the
Proj.pd commit in my efforts to check out the new
mmap code via CPAN Testers. The first reports out
of the gate with PDL-2.4.10_001 had crashes during
the builds of the PROJ4 stuff.
Since there was a single fix related to PROJ4,
I decided to revert that change to see if it was
the origin of the PROJ4 problems from the CPAN
Testers or if it was from the File::Map version
of the mapflex and mapfraw.
The result was the crash during the PROJ4 build
that were seen with some of the _001 testers
reports were not reproduced with either the _002
or _003 PDL developers release. It appears that
the problems are not coupled and that the new
mmap code appears to work (mostly).
I've just reverted the reversion of the original
commit so the next CPAN Developers release will
again feature the Proj.pd with the 4.8.0 fix.
With the re-reverted code, I am able to build ok
on cygwin with proj 4.6.1. The previous problem
may have been some kind of version skew. I'll
continue to investigate here as well.
--Chris
On 4/8/2012 10:18 PM, David Mertens wrote:
On Sun, Apr 8, 2012 at 7:23 PM, Sisyphus<[email protected]> wrote:
----- Original Message ----- From: "chm"<[email protected]>
To: "Sisyphus"<[email protected]>
Cc:<[email protected]>
Sent: Monday, April 09, 2012 1:39 AM
Subject: Re: [Perldl] CHM/PDL-2.4.10_002.tar.gz released to CPAN
I think a combination of the PDL-2.4.10 version
of Proj.pd with the new code for 4.8.0 implemented
with appropriate #ifdefs on PROJ4 version should
work with old and new proj installs since it would
use the current stable implementation for pre-4.8.0
verions of libproj and then the new code for more
recent versions.
It shouldn't be that complicated and I've yet to *see* any evidence that
it is, having invested quite a few hours in trying to find such evidence.
In fact, I've yet to *see* any evidence that there is *any* problem with
the proj.pd I committed recently. (If someone could actually send me such
evidence, that might ease my frustration. Otherwise I'll just have to wait
until the cpantesters web server is up and running again.)
Cheers,
Rob
______________________________**_________________
Perldl mailing list
[email protected]
http://mailman.jach.hawaii.**edu/mailman/listinfo/perldl<http://mailman.jach.hawaii.edu/mailman/listinfo/perldl>
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.
Chris may have been a bit hasty in calling your contribution "broken."
That definitely was not my intent and opining about any
given code version should best be left to the test
results and not hasty guesses---especially in email.
My apologies there also, Rob.
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.
David
_______________________________________________
Perldl mailing list
[email protected]
http://mailman.jach.hawaii.edu/mailman/listinfo/perldl
