🚀 go-pugleaf

In article <1990Jan15.020327.13614@athena.mit.edu> rlcarr@space.mit.edu (the Wizard of Speed and Time) writes:
>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?

void * is an ANSI-ism that means 'take any kind of pointer'.  char * is the
pre-ANSI way of asking for a generic pointer, which meant you had to cast
the pointer you were passing to char *.  I suggest changing the char *
declarations to void *, or simply #if 0'ing out the char * definitions.


  *****
=*|_o_o|\\=====Doug Walker, Software Distiller=======================
 *|. o.| ||
  | o  |//     Apologies to those who send me mail.  About 80% of
  ======       my replies bounce...
usenet: ...mcnc!rti!sas!walker   plink: dwalker  bix: djwalker