Date: Mon, 26 Aug 1996 10:19:39 -0400 (EDT) From: Tim Vanderhoek <hoek@freenet.hamilton.on.ca> To: Robert Nordier <rnordier@iafrica.com> Cc: hoek@freenet.hamilton.on.ca, questions@FreeBSD.org Subject: Re: Programming Question Message-ID: <Pine.SOL.3.91.960826101246.27905B-100000@james.freenet.hamilton.on.ca> In-Reply-To: <199608260812.KAA02909@eac.iafrica.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 26 Aug 1996, Robert Nordier wrote: > Note that 'typedef' doesn't create types, just synonyms for existing > types. So the assignment <AT> = <int> doesn't involve a type > conflict in any sense. If I set a typedef, it's because I want all variables in a given group to be that type. I might later decide to change that (ie. int isn't quite large enough when someone decides to check a doc with 66000 words; let's try long int). All of a sudden, a bunch of errors will spew all over the place. I'd prefer to know about them now, rather than later. The exception, of course, is when passing a variable of type <AT> (where <AT> == <int>) to a library function expecting an int. In all other places a warning would be nice... :( > For automated nitpicking, I like 'lclint' (from the 'lcc' compiler > people): > > | LCLint 2.0 --- 21 Mar 96 > | [ warnings deleted ] > | > | Finished LCLint checking --- 2 code errors found I like it! -- Outnumbered? Maybe. Outspoken? Never! tIM...HOEk
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.SOL.3.91.960826101246.27905B-100000>