Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!usc!snorkelwacker!bloom-beacon!athena.mit.edu!rlcarr
From: rlcarr@athena.mit.edu (the Wizard of Speed and Time)
Newsgroups: comp.sys.amiga.tech
Subject: Lattice C Header ERROR!
Summary: stdlib.h, string.h conflict
Message-ID: <1990Jan15.020327.13614@athena.mit.edu>
Date: 15 Jan 90 02:03:27 GMT
Sender: news@athena.mit.edu (News system)
Reply-To: rlcarr@space.mit.edu (the Wizard of Speed and Time)
Organization: a Mike Jittlov Fan
Lines: 24

I have Lattice C 5.04 (haven't applied either the 5.04a or 5.04b patches yet)
and have discovered that the string.h and stdlib.h have conflicting 
prototypes in them.  Specifically, one file has various memory functions
(like memcpy) as taking void *'s while the other file shows them taking
char *'s.  Which is it?  And have the patches fixed it?

% setenv FLAME on
How could Lattice not have found this out?  Using string.h and stdlib.h
together is a very basic thing to do.  I really like their product, but
errors like this drive me CRAZY!
% setenv FLAME off

Sigh.

Rich Carreiro - Most Biased Boston Celtics Fan!   "So long, farewell, and may
ARPA: rlcarr@space.mit.edu                         the forces of evil become
UUCP: ...!mit-eddie!space.mit.edu!rlcarr           confused on the way to your
BITNET: rlcarr@space.mit.edu                       door!" - George Carlin

--
Rich Carreiro - Most Biased Boston Celtics Fan!   "So long, farewell, and may
ARPA: rlcarr@space.mit.edu                         the forces of evil become
UUCP: ...!mit-eddie!space.mit.edu!rlcarr           confused on the way to your
BITNET: rlcarr@space.mit.edu                       door!" - George Carlin