Path: utzoo!censor!geac!torsqnt!news-server.csri.toronto.edu!cs.utexas.edu!yale!hsdndev!cmcl2!lanl!gam
From: gam@lanl.gov (Gim Mark)
Newsgroups: comp.windows.open-look
Subject: Re: XView and lint....
Summary: xview, sunview: avoid lint
Message-ID: <7881@lanl.gov>
Date: 5 Dec 90 14:35:06 GMT
References: <zimy1k7@openlook.Unify.Com>
Organization: Los Alamos Natl Lab, Los Alamos, N.M.
Lines: 22

In article <zimy1k7@openlook.Unify.Com>, kbj@jupiter.risc.com (Ken Johnson) writes:
> 
> I'm trying to get in the habit of writing 'good code' so I am beginning to
> use lint.  lint pukes out dozens of pages of warnings about xv calls.  Any ideas
> on options that will prevent this so I don't have to wade thru pages of stuff
> to find the few useful messages?
> 
> 
> Ken Johnson                             Phone: 805-373-4487

Here's what Lew Yobs (lewy@corp.sun.com) in customer support at Sun had to say
about lint and SunView:

	The suntool, sunwindow lint libraries have had problems
	for several releases now and considering the volume 
	of info running lint on the simple test case produces
	under SunOS4.1 (worse than with SunOS 4.0) using
	lint is probably best avoided with those libraries.

Evidently the same holds for XView.

Graham Mark