I wonder if there is a way we could bulletproof the XS->C build process. For example, xsubpp could generate an assertion that would check for #defined values that match variable names. The question is how to avoid cases where this is exactly what you want. Maybe generate a warning instead?
--Chris On 6/16/2015 04:19, sisyph...@optusnet.com.au wrote: > -----Original Message----- From: Ed > Sent: Tuesday, June 16, 2015 5:48 PM > To: sisyph...@optusnet.com.au ; Bob Free ; Chris Marshall > Cc: pdl-devel@lists.sourceforge.net ; kmx > Subject: Re: [Pdl-devel] CHM/OpenGL-0.6704_01.tar.gz uploaded to CPAN > >> I'll bet "far" and "near" are #defined to blank, and are a Windows >> pointer-size related issue. > > Definitely Windows related. > > No problem if windows.h doesn't get included but, of course, the > standard XS headers inevitably pull in that header. > And the offending header file (minwindef.h or perhaps windef.h in > some cases, I think) is thus ultimately included. > > Cheers, > Rob ------------------------------------------------------------------------------ _______________________________________________ pdl-devel mailing list pdl-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/pdl-devel
