Xref: utzoo comp.lang.c:30353 comp.unix.xenix:12447
Path: utzoo!attcan!uunet!cs.utexas.edu!samsung!dali.cs.montana.edu!uakari.primate.wisc.edu!zaphod.mps.ohio-state.edu!sdd.hp.com!elroy.jpl.nasa.gov!ames!ptolemy!eos!shelby!neon!Gang-of-Four!dkeisen
From: dkeisen@Gang-of-Four.Stanford.EDU (Dave Eisen)
Newsgroups: comp.lang.c,comp.unix.xenix
Subject: Almost ANSI compiler
Message-ID: <1990Jul17.205919.2113@Neon.Stanford.EDU>
Date: 17 Jul 90 20:59:19 GMT
Sender: news@Neon.Stanford.EDU (USENET News System)
Organization: Sequoia Peripherals
Lines: 20

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@Gang-of-Four.Stanford.EDU           Office: (415) 967-5644
1447 N. Shoreline Blvd.
Mountain View, CA 94043