>strlcpy is not in POSIX and never will be.
So what? There are enough dumb spec in POSIX to show that it's not the ultimate reference in
> It doesn't actually do what any sane person would
want, unless you don't really care what ends up in the destination string. But if you don't
care, why call it at all?
That's false: when you don't make a mistake the destination string is correct, when you do
make a mistake, then even if the destination string is incorrect at least this isn't (normaly)
a security issue, which is much better that what those other string copy provides.