Path: utzoo!attcan!uunet!husc6!cca!g-rh From: g-rh@cca.CCA.COM (Richard Harter) Newsgroups: comp.std.c Subject: Re: Defining Portable (Was: Invalid pointer addresses) Message-ID: <33450@cca.CCA.COM> Date: 19 Sep 88 05:21:30 GMT References: <12088@steinmetz.ge.com> <8453@smoke.ARPA> <10595@ulysses.homer.nj.att.com> <1988Sep16.170408.16304@utzoo.uucp> <33423@cca.CCA.COM> <8518@smoke.ARPA> Reply-To: g-rh@XAIT.Xerox.COM (Richard Harter) Organization: Xerox Corporation, Cambridge, Massachusetts Lines: 24 In article <8518@smoke.ARPA> gwyn@brl.arpa (Doug Gwyn (VLD/VMB)) writes: >In article <33423@cca.CCA.COM> g-rh@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.