Xref: utzoo comp.std.c:985 comp.lang.c:17352
Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!sharkey!atanasoff!hascall
From: hascall@atanasoff.cs.iastate.edu (John Hascall)
Newsgroups: comp.std.c,comp.lang.c
Subject: VAX11C memcpy (was Re: realloc)
Message-ID: <941@atanasoff.cs.iastate.edu>
Date: 1 Apr 89 17:37:25 GMT
References: <10170@bloom-beacon.MIT.EDU> <10032@ihlpb.ATT.COM> <9118@alice.UUCP> <1917@dataio.Data-IO.COM>
Reply-To: hascall@atanasoff.cs.iastate.edu (John Hascall)
Organization: Iowa State Univ. Computation Center
Lines: 24

In article <1917@dataio.Data-IO.COM> bright@dataio.Data-IO.COM (Walter Bright) writes:
>In article <9118@alice.UUCP< ark@alice.UUCP (Andrew Koenig) writes:
 
><In article <10032@ihlpb.ATT.COM<, gregg@ihlpb.ATT.COM (Wonderly) writes:
><Of course, not all C implementations behave this way.  This
><leaves C programmers in a bind: rely on this behavior or not?  If
 
>I am involved daily with porting code between PCs, Suns, Apples, Vaxes,
>For instance, BSD Unix doesn't have memcpy, so I have:
 
>#if BSDUNIX || VAX11C
>char *memcpy(t,f,n)

   [... code omitted ...]

>#endif

>(VAX11C is my euphamism for DEC's C compiler.)

   ????

   The VAXC library has memcpy.  What gives?

John Hascall / ISU Comp Center