Path: utzoo!utgpu!watserv1!watmath!att!rutgers!uwm.edu!zaphod.mps.ohio-state.edu!usc!snorkelwacker!bu.edu!mirror!necntc!necssd!harrison
From: harrison@necssd.NEC.COM (Mark Harrison)
Newsgroups: comp.lang.c
Subject: Re: Can lint help an ANSI-C programmer?
Message-ID: <370@necssd.NEC.COM>
Date: 4 Jun 90 14:58:01 GMT
References: <6328.265D8157@puddle.fidonet.org> <1754@tkou02.enet.dec.com> <36985@think.Think.COM>
Organization: NEC America Inc. SSD, Irving, TX
Lines: 15

In article <36985@think.Think.COM>, barmar@think.com (Barry Margolin) writes:

>                                                              It is
> traditional that C compilers do minimal checking, and lint is used when the
> programmer wants extensive checking.  This tradition is fading, though, as
> C has reached more environments.  For instance, integrated development
> systems such as Turbo C generally ignore this tradition.  GNU C also does
> lots of checking (although there are options to control it) because the GNU
> developers don't believe in tradition for its own sake.

Turbo C also has options to control how much checking is performed.
-- 
Mark Harrison             harrison@necssd.NEC.COM
(214)518-5050             {necntc, cs.utexas.edu}!necssd!harrison
standard disclaimers apply...