Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/5/84; site tove.UUCP
Path: utzoo!watmath!clyde!cbosgd!ihnp4!mhuxn!mhuxb!mhuxr!ulysses!allegra!mit-eddie!godot!harvard!seismo!umcp-cs!tove!mark
From: mark@tove.UUCP (Mark Weiser)
Newsgroups: net.lang.c
Subject: Re: SIZEOF
Message-ID: <116@tove.UUCP>
Date: Mon, 4-Feb-85 22:37:43 EST
Article-I.D.: tove.116
Posted: Mon Feb  4 22:37:43 1985
Date-Received: Thu, 7-Feb-85 02:41:10 EST
References: <347@ecr.UUCP> <393@rlgvax.UUCP> <260@gumby.UUCP> <1071@amdahl.UUCP>
Reply-To: mark@tove.UUCP (Mark Weiser)
Organization: U of Maryland, Laboratory for Parallel Computation, C.P., MD
Lines: 25

In article <1071@amdahl.UUCP> gam@amdahl.UUCP (gam) writes:
>> > Anyone who has made much effort at porting C code has encountered lots of
>> > problems, all too many of which are due to people misusing the language.
>> > Many of those can be avoided by using "lint".  Go forth and do so.
>> > 
>>    With regard to lint:
>> 
>>    1) Most people working in a Unix environment never use it, because they
>>       don't have to.
>>    Human nature being what it is, "go forth and use lint" should get approx-
>> imately the same enthusiastic response as "go forth and sin no more."
>
>Lint is widely used here....porting programs from other systems would be
>a painful task without lint.
>

We have Pyramid's and Vaxes as our main machines.  If your code passes
lint, it is likely to run both, in spite of the fact that the
stack is used differently, the byte orders are reversed, and they
require different word alignments when acessing structures.  Lint
is handy
-- 
Spoken: Mark Weiser 	ARPA:	mark@maryland	Phone: +1-301-454-7817
CSNet:	mark@umcp-cs 	UUCP:	{seismo,allegra}!umcp-cs!mark
USPS: Computer Science Dept., University of Maryland, College Park, MD 20742