Path: utzoo!mnetor!uunet!lll-winken!lll-lcc!ames!ncar!gatech!uflorida!codas!cpsc6a!atl2!akgua!mtunx!whuts!homxb!hropus!jgy
From: jgy@hropus.UUCP (John Young)
Newsgroups: comp.lang.c
Subject: Re: strcpy
Message-ID: <98@hropus.UUCP>
Date: 29 Mar 88 05:07:42 GMT
References: <12678@brl-adm.ARPA>
Organization: Bell Labs, Holmdel, NJ
Lines: 15

> In article <90@hropus.UUCP> John Young <hropus!jgy> writes:
> >If the "contents of the destination string past the null character"
> >are not guaranteed why would anyone use strcpy()? 
> 
> Well, at the risk of sounding flippant, one would use strcpy() to make
> a copy of a string.  I personally don't use strcpy() for any other
> reason, and I don't see how writing past the null but within the
> bounds of the destination array would preclude this.
> 
> [In a previous posting I retracted my statement that strcpy() could
> write something past the null in the destination string.]
> 

There was no mention of "within the bounds of the destination array"
in the origonal posting.  How would you suggest strcpy() check for
this?  Good thing you retracted your statement (I didn't see it!)