[Info-vax] c 7.3 - Why MAYLOSEDATA3 for long pointer math?

[John Reagan]

On Friday, March 13, 2015 at 11:16:58 PM UTC-4, Steven Schweda wrote:

>    You seem to over-estimate my ability to persuade various
> keepers of open-source software to add piles of VMS-specific
> #pragma garbage to their source in order to work around such
> goofy behavior from a compiler on a system about which they
> typically care hardly a whit.  (And/or my willingness to
> try to explain why the difference between two 32-bit pointers
> should be a 64-bit entity.  I nearly wore out my welcome
> trying to deal with the not-NULL-terminated argv[] on Alpha
> with /POINTER_SIZE=64=ARGV.)  But thanks for the advice.

I get your point (and sarcasm).  For the /POINTER_SIZE=64=ARGV, that was clearly a compiler bug that was fixed with an ECO.  Surely open-source software isn't chocked full of conditionals to work around platform or tool bugs?

If you use /FIRST_INCLUDE, you might be able to turn it off without spreading changes across lots of code.