Re: [Pdl-devel] Insert C code before '#include "EXTERN.h"'

2015-05-25 Thread David Mertens
But aren't there basic ways to work around this? Why don't they prefix all struct declarations with something like proj_ or libproj_? They could then include #defines that provide like-named symbols without the prefix UNLESS you have #defined some sensibly named symbol, like PROJ_NO_NAMESPACE_POLUT

Re: [Pdl-devel] Insert C code before '#include "EXTERN.h"'

2015-05-25 Thread sisyphus1
Hi David, I did suggest something like that, even though I think it’s messy. Would I need to define PROJ_NO_NAMESPACE_POLUTION when building the proj library ? ... or would I need to define it only when building PDL::GIS::Proj ? (There’s no problem until winreg.h gets included – and that doesn’t

Re: [Pdl-devel] PDL-2.008 released to CPAN

2015-05-25 Thread Chris Marshall
It appears the problems with the PAUSE indexer are not preventing PDL-2.008 being available. We're working on cleaning up these issues and will release a PDL-2.009 soon. Testing and feedback on PDL-2.008 is welcome! --Chris On 5/24/2015 19:46, Chris Marshall wrote: > There appears to be a proble

[Pdl-devel] pdldoc.db has spurious paths on cygwin

2015-05-25 Thread Chris Marshall
When I run 'pdldoc slice' for the PDL-2.008 install I get the following error: pdldoc slice can't find file '/home/chm/local/lib/perl5/cygwin-thread-multi/PDL/../../../../../../../cygdrive/e/chm/local/lib/perl5/cygwin-thread-multi/PDL/Slices.pm' at /home/chm/local/lib/perl5/cygwin-thread-mul

Re: [Pdl-devel] pdldoc.db has spurious paths on cygwin

2015-05-25 Thread Chris Marshall
Apparently, if I set PERL5LIB to a path with the same root as the install drive, then the docs database is built consistently and then works with the cross-filesystem version of PERL5LIB or the same-filesystem one. E.g., PERL5LIB=/cygdrive/e/chm/local/lib/perl5 make docs database p

Re: [Pdl-devel] Insert C code before '#include "EXTERN.h"'

2015-05-25 Thread David Mertens
The basic idea behind this approach is that the *compiler* only thinks of the identifiers by their full (prefixed) names, but the preprocessor knows how to translate short names into full names. Thus the proj binaries will only know about the full names. As long as users leave the name resolution

Re: [Pdl-devel] Insert C code before '#include "EXTERN.h"'

2015-05-25 Thread sisyphus1
From: David Mertens Sent: Tuesday, May 26, 2015 7:21 AM To: Sisyphus Cc: Chris Marshall ; pdl-devel@lists.sourceforge.net Subject: Re: [Pdl-devel] Insert C code before '#include "EXTERN.h"' > The basic idea behind this approach is that the *compiler* only thinks of > the identifiers by their full

Re: [Pdl-devel] Insert C code before '#include "EXTERN.h"'

2015-05-25 Thread sisyphus1
-Original Message- From: sisyph...@optusnet.com.au Sent: Tuesday, May 26, 2015 9:40 AM To: David Mertens Cc: pdl-devel@lists.sourceforge.net Subject: Re: [Pdl-devel] Insert C code before '#include "EXTERN.h"' > OK - all they would need to do is change: > > typedef union { double f; int

Re: [Pdl-devel] Insert C code before '#include "EXTERN.h"'

2015-05-25 Thread David Mertens
Yeah, I hope that the Proj folks just change the identifiter. This sort of nonsense is one of the major reasons I prefer Perl over C: proper namespace handling. I've gotten much more skilled at it lately, but I wish I didn't need to. :-) On Mon, May 25, 2015 at 8:22 PM, wrote: > -Original Me