🚀 go-pugleaf

Chris Gray writes:

>Folks! Use full prototypes. Turn on all possible warning flags. Make your
>code compile clean. Use some fairly standard programming style. Make your
>file global variables instantly distinguishable from your local ones. Avoid
>inter-file globals (externs) like the plague. Don't overuse macros. Make
>ALL macro names in all upper case (except perhaps true/false).

Wow.  I can't agree with you more.  I learned ANSI C programming while
I worked at Microsoft.  I can't tell you how many times function prototypes
have saved my skin.  It seems all the source code I look at in the UNIX
world is non-ANSI, this sorta bugs me.  I also agree with you regarding
always using all possible warning flags, however it becomes difficult
to do this when the OSCALLS.H header file on your system looks like this:

extern int access();
...

I suppose I could make my own stinking header file which has stuff that
looks like: 

extern int access (char *, int);

Would it really be worth it?

mikeh