Prev: composition and bad_alloc
Next: ANN: Library dependency graphs tool status update and questions
From: Jorgen Grahn on 7 Jul 2008 08:35
On Thu, 3 Jul 2008 08:55:08 CST, Francis Glassborow
<francis.glassborow(a)btinternet.com> wrote:
> Mathias Gaunard wrote:
>
>> Apart from the part it's perfectly useless Microsoft-specific
>> monstruosity and duplicates the standard strncpy, I do not think there
>> is any.
>
> You are entitled to your opinion, however it is no longer and entirely
> MS function and it does not in fact duplicate strncpy though there is a
> considerable overlap.

True. It seems to have more overlap with strlcpy() though (enough
overlap to make them equivalent, I wonder?)

strlcpy() was introduced in OpenBSD back in 1998, and is fairly well
known among Unix programmers. I suspect that many people will choose
strlcpy() in the future too, for technical, practical and political
reasons ...

Personally, I'll use std::string.

/Jorgen

--
// Jorgen Grahn <grahn@ Ph'nglui mglw'nafh Cthulhu
\X/ snipabacken.se> R'lyeh wgah'nagl fhtagn!

[ See http://www.gotw.ca/resources/clcm.htm for info about ]
[ comp.lang.c++.moderated. First time posters: Do this! ]

First  |  Prev  | 
Pages: 1 2 3 4 5 6
Prev: composition and bad_alloc
Next: ANN: Library dependency graphs tool status update and questions