🚀 go-pugleaf

Larry W. Virden <lwv26@cas.org> writes: 

> These suggestions are only true if you plan on compiling all the pieces of
> your program together each time you do a compile .  Many folk use libraries,
> and thus find it extremely difficult to get good warnings about arguments
> passed to various functions, etc.

IMNSHO, the interface (i.e., arguments and return value) for EVERY
library function should be completely defined in user-accessible
header files. There even are utilities for automatically generating
ANSI C prototypes. (I believe one is called "protoize".) I'm a big
believer in edit- and compile-time (as opposed to run-time) checking,
but by using the finer features of Emacs and GCC (like
auto-indentation, s-expressions, and prototypes), I never need "lint"
to generate code that's pretty clean before it's first executed.
_______________________________________________________________________________

Tony Silva				tel:      (617)890-4200
Atlantic Aerospace Electronics Corp.	FAX:      (617)890-0224
470 Totten Pond Road			Internet: tsilva@aaec.com
Waltham, MA 02154