Path: utzoo!attcan!uunet!husc6!bloom-beacon!athena.mit.edu!scs
From: scs@athena.mit.edu (Steve Summit)
Newsgroups: comp.lang.c
Subject: using standard interfaces (was: Re: Explanation, please!)
Message-ID: <7076@bloom-beacon.MIT.EDU>
Date: 16 Sep 88 00:07:51 GMT
References: <485.231DAAC3@stjhmc.fidonet.org> <725@proxftl.UUCP>
Sender: daemon@bloom-beacon.MIT.EDU
Reply-To: scs@adam.pika.mit.edu (Steve Summit)
Lines: 19

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.

The reason we keep pointing out the existence of standard
functions to those who would rather (or have to) roll their own
is to encourage people to start using the standard interface, by
writing their own function with the same name and parameters,
rather than sticking special-purpose code in-line, or inventing
some new name.  This way the program can take advantage of
standardized, optimized implementations when they become
available (for instance when the program is ported to a different
system which has them).

                                            Steve Summit
                                            scs@adam.pika.mit.edu