Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!mcsun!ukc!pyrltd!root44!gwc
From: gwc@root.co.uk (Geoff Clare)
Newsgroups: comp.sys.hp
Subject: Re: bcopy v.s. memcpy (was BSD and HPUX, The Questions Continue...)
Message-ID: <2727@root44.co.uk>
Date: 31 May 91 13:26:00 GMT
References: <1991May2.202710.5152@odin.diku.dk> <5570626@hpfcdc.HP.COM> <CEDMAN.91May8203446@lynx.ps.uci.edu> <TML.91May9235144@hemuli.tik.vtt.fi> <JBW.91May24192706@bigbird.bu.edu> <9674@cognos.UUCP>
Organization: UniSoft Ltd., London, England
Lines: 12

In <9674@cognos.UUCP> jimp@cognos.UUCP (Jim Patterson) writes:

>memmove is part of the ANSI C standard, and guarantees
>proper handling of overlapping moves. I believe that it's part of
>POSIX as well, since POSIX requires ANSI C.

No, POSIX.1 only requires selected parts of ANSI C, not the whole thing.

The mem*() functions are not required by POSIX.1.
-- 
Geoff Clare <gwc@root.co.uk>  (Dumb American mailers: ...!uunet!root.co.uk!gwc)
UniSoft Limited, London, England.   Tel: +44 71 729 3773   Fax: +44 71 729 3273