I looked at this closer and stpncpy() is different from strncopy()
so unlike
strcopy() => stpcpy()
we won't be able to do
strncopy() => stpncpy()
ast strncopy() usage is to prevent overflow of the destination string
so in most cases the size argument is >> strlen(source)
and in that case stpncpy() will fill the difference with '\0' -- a waste
unless an app really needs the '\0''s
without the '\0' fill property the ast usage could be adjusted
_______________________________________________
ast-developers mailing list
[email protected]
http://lists.research.att.com/mailman/listinfo/ast-developers
