Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!zaphod.mps.ohio-state.edu!uakari.primate.wisc.edu!dogie.macc.wisc.edu!decwrl!shelby!csli!poser
From: poser@csli.Stanford.EDU (Bill Poser)
Newsgroups: comp.lang.c
Subject: Re: strncpy
Keywords: strncpy null termination
Message-ID: <11515@csli.Stanford.EDU>
Date: 22 Dec 89 10:39:00 GMT
References: <11509@csli.Stanford.EDU> <8313@stiatl.UUCP> <621@buster.irby.com>
Sender: poser@csli.Stanford.EDU (Bill Poser)
Reply-To: poser@csli.stanford.edu (Bill Poser)
Organization: Center for the Study of Language and Information, Stanford U.
Lines: 10

In article <621@buster.irby.com> rli@buster.irby.com (Buster Irby) writes:
>
>CAUTION: There is a lot of existing software in the world that
>would break if the operation of strncpy or any other standard
>library function were suddenly changed.

I at least was not calling for a redefinition of strncpy in my
posting, only asking whether there was a good reason for it to behave
as it does. My own null-terminating version is called tstrncpy, and
I would guess that other people's have distinct names too.