Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 6/24/83; site utah-gr.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!mhuxr!mhuxb!mhuxn!mhuxm!mhuxj!houxm!whuxlm!harpo!decvax!genrad!panda!talcott!harvard!seismo!utah-cs!utah-gr!donn
From: donn@utah-gr.UUCP (Donn Seeley)
Newsgroups: net.wanted.sources,net.unix-wizards
Subject: Re: Wanted: Long Identifier Hunter
Message-ID: <1321@utah-gr.UUCP>
Date: Tue, 29-Jan-85 01:51:14 EST
Article-I.D.: utah-gr.1321
Posted: Tue Jan 29 01:51:14 1985
Date-Received: Thu, 31-Jan-85 01:22:14 EST
References: <3496@mit-eddie.UUCP>
Organization: University of Utah CS Dept
Lines: 40
Xref: watmath net.wanted.sources:405 net.unix-wizards:11785


	From: shawn@mit-eddie.UUCP (Shawn McKay)

	I am looking for something to run over broken BSD software,
	that will aid me in finding [long identifier clashes]...

[If the software is broken, then why are you stealing it?]

Rather than write your own long-identifier detector or borrow some
bug-ridden net.sources hack, I suggest you make use of a little-known
and (when known) oft-ignored program named 'lint'.

------------------------------------------------------------------------
% cat problem.c
main()
{
	DonotUseLongIdentifiersOnSoftwareYouWishToShare();
	DonotUseLongIdentifiersOnSoftwareYouWishToDistribute();
	exit( 0 );
}

DonotUseLongIdentifiersOnSoftwareYouWishToShare()
{
	return;
}

DonotUseLongIdentifiersOnSoftwareYouWishToDistribute()
{
	return;
}
% lint -hp problem.c
problem.c:
donotu multiply declared	problem.c(9)  ::  problem.c(14)
%
------------------------------------------------------------------------

Charter member of the Society for the Prevention of Cruelty to Software,

Donn Seeley    University of Utah CS Dept    donn@utah-cs.arpa
40 46' 6"N 111 50' 34"W    (801) 581-5668    decvax!utah-cs!donn