Path: utzoo!attcan!uunet!husc6!ukma!uflorida!novavax!proxftl!bill
From: bill@proxftl.UUCP (T. William Wells)
Newsgroups: comp.lang.c
Subject: Re: using standard interfaces (was: Re: Explanation, please!)
Message-ID: <783@proxftl.UUCP>
Date: 18 Sep 88 09:30:45 GMT
References: <485.231DAAC3@stjhmc.fidonet.org> <725@proxftl.UUCP> <7076@bloom-beacon.MIT.EDU>
Reply-To: bill@proxftl.UUCP (T. William Wells)
Organization: Proximity Technology, Ft. Lauderdale
Lines: 20
Summary:
Expires:
Sender:
Followup-To:
Distribution:
Keywords:

In article <7076@bloom-beacon.MIT.EDU> scs@adam.pika.mit.edu (Steve Summit) writes:
: A while back, somebody wrote (explaining why they hadn't and/or
: wouldn't use a newly standardized function):
:
:       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.

That was me talking.  And you have the story wrong.  Duff wrote
an unrolled loop some time in the past to do approximately what
memcpy does, inline, before memcpy was generally available;
moreover, the circumstances were such that even if these routines
had been available, it wouldn't have been good programming for
him to use them.

Please avoid taking things out of context.

---
Bill
novavax!proxftl!bill