Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!mailrus!cornell!uw-beaver!ssc-vax!uvicctr!tholm From: tholm@uvicctr.UUCP (Terrence W. Holm) Newsgroups: comp.os.minix Subject: memcpy(3) Message-ID: <503@uvicctr.UUCP> Date: 18 Sep 88 17:25:44 GMT Reply-To: tholm@uvicctr.UUCP (Terrence W. Holm) Organization: University of Victoria, Victoria B.C. Canada Lines: 24 > From: chip@vector.UUCP (Chip Rosenthal) > > In article <496@uvicctr.UUCP> tholm@uvicctr.UUCP (Terrence W. Holm) writes: > >There follows an implementation of memcpy(3), memccpy(3), > >memchr(3), memcmp(3) and memset(3) for MINIX. Please consider > > It might worth playing some games with these. I would think that memcpy() > is one of the cases where you are willing to give a little ugliness for > performance. Yes, I agree. But you must have noticed that my mission is to supply MINIX with a useful, documented library, not to waste time with small performance details - which are mute once we consider the whole picture. If you want to really help the MINIX community, I can supply you with a list of more important topics. > > There was a recent discussion in comp.lang.c about using "Duff's Device" Yes, I teach all my 1st years to write code this way :-) :-) Terrence W. Holm