Kurt Kuzba,
  In a message on 16 September, to Kenneth Dunn, wrote :

KK> KD> RT>   char name[9][9];
KK> KD> RT>   strcpy(name[0],"Trevor");
KK> KD>   strncpy() is safer, it is like strcpy() except it takes
KK> KD>   another agrument limiting the maximum number of
KK> KD>   characters to copy.
KK>    Right. You can never be too safe when it comes to observing
KK>    character array boundaries. Bugs can creep in unseen.

Unfortunately I forgot that strncpy doesn't automatically 
null terminate. Which can be just as much of a problem as
overwriting. 

What I find is the strn* functions are a little inconsistant. 
My reasoning: the logical design would be copy at most n-1 and 
terminate with a null character instead of having to allocate 
n+1 characters and putting a null character on the end if n items 
where copied. 

Never mind, just my line of thinking. Knew there was a good reason
for using my own custom fuctions :-)

   
...
 * ATP/Linux 1.42 * 
--- Renegade v10-05 Exp