Almost ANSI compiler

[Dave Eisen]

We recently upgraded to SCO Xenix 2.3.2 with Microsoft C Compiler 5.1. It
is somewhat ANSIish --- it accepts the const keyword, void *, etc. The problem
is that many of the functions declared in the header files are declared incorrectly.

For example, strcpy is declared char *strcpy (char *, char *) instead of
char *strcpy (char *, const char *), malloc is defined to be of type char * instead
of void *, and so on. These problems lead to a flurry of compiler warnings
if these functions are used without casts to the "incorrect" types. 

Is there any harm in changing around the header of files or am I forced to
write strcpy (dest, (char *) src) whenever I want to call strcpy?



 
--
Dave Eisen                      	    Home: (415) 323-9757
dkeisen at Gang-of-Four.Stanford.EDU           Office: (415) 967-5644
1447 N. Shoreline Blvd.
Mountain View, CA 94043