lint, pointers, 0 (what else?)

[Doug Gwyn <gwyn>]

> The result of using this system is that you know your programs will get
> enough space on strange hardware. If it needs things that are too big, it
> won't compile.

I think this is backwards.  How about writing your code in terms of
parameters describing the system (such as those in <limits.h>), rather
than writing code that does not work on systems having perfectly
reasonable arithmetic properties that just don't happen to be what
you had when you wrote the code.

I see the ANSI C committee is attempting to fix the botched floating-
point parameters in /usr/group's published set of implementation limits.
There are more parameters needed than what they have so far (see the
UNIX System V <values.h> for example).