Defining Portable (Was: Invalid pointer addresses)

[Richard Harter]

In article <8518 at smoke.ARPA> gwyn at brl.arpa (Doug Gwyn (VLD/VMB) <gwyn>) writes:
>In article <33423 at cca.CCA.COM> g-rh at XAIT.Xerox.COM (Richard Harter) writes:
>-*note: In a VMS C port recently we got bitten on the monocase externals
>-gotcha.  A nice tool to have would be one that reports all potential
>-identifier problems.

>UNIX "lint -p" does this.

Among other things.  I had more in mind something that specifically dealt with
identifier problems, i.e. potential case conflicts and identifier length
issues with the ability to set ambiguity lengths and maximum lengths as
options.  It's a trivial matter to set up a program to do this, given a list
of all the externals referenced and declared.  Maybe you can get the right
list from cxref.  Come to think on it, I've got a C cross reference program
that does this for functions.  It would be a simple matter to expand it to
put out external variables as well.  Never mind.



-- 

In the fields of Hell where the grass grows high
Are the graves of dreams allowed to die.
	Richard Harter, SMDS  Inc.