Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!bu.edu!nntp-read!jbw From: jbw@bigbird.bu.edu (Joe Wells) Newsgroups: comp.sys.hp Subject: Re: BSD and HPUX, The Questions Continue... Message-ID: Date: 24 May 91 23:27:06 GMT References: <1991May2.202710.5152@odin.diku.dk> <5570626@hpfcdc.HP.COM> Sender: news@bu.edu Organization: Boston University Computer Science Department Lines: 17 In-reply-to: tml@tik.vtt.fi's message of 10 May 91 03:51:44 GMT tml@tik.vtt.fi (Tor Lillqvist) writes: I don't know if this is entirely good news... Doesn't this mean that now also on HP-UX you can get away with sloppy programming style (using the b* and index functions even if ANSI C and POSIX mandate mem* and strchr)? bcopy guarantees correct overlapping moves. memcpy does not. When ANSI C or POSIX provide us with a function that is guaranteed to handle overlapping moves correctly, then you can justify your position. Until then, please don't get rid of bcopy. (On the other hand, bzero and bcmp can probably be safely #defined away right now.) -- Enjoy, Joe Wells