Path: utzoo!attcan!uunet!husc6!mailrus!uflorida!novavax!proxftl!bill
From: bill@proxftl.UUCP (T. William Wells)
Newsgroups: comp.lang.c
Subject: Re: Explanation, please!
Message-ID: <725@proxftl.UUCP>
Date: 8 Sep 88 00:55:06 GMT
References: <485.231DAAC3@stjhmc.fidonet.org>
Reply-To: bill@proxftl.UUCP (T. William Wells)
Organization: Proximity Technology, Ft. Lauderdale
Lines: 16
Summary:
Expires:
Sender:
Followup-To:
Distribution:
Keywords:

In article <485.231DAAC3@stjhmc.fidonet.org> jim.nutt@p11.f15.n114.z1.fidonet.org (jim nutt) writes:
:  ->    I doubt that memcpy even existed then; and it is *not* standard
:  ->    now.  Perhaps it will be several years after the ANSI standard is
:  ->    adopted, but not till then.
:
: memcpy() IS in the ansi standard library, along with a similar
: function called memmove().

Yes, I know.  I said "it isn't standard", not "it isn't in the
standard".  The difference is that "it isn't standard" means that
you can't write portable code that assumes that it exists; the
other should be obvious.

---
Bill
novavax!proxftl!bill