|
|
Subscribe / Log in / New account

The ups and downs of strlcpy()

The ups and downs of strlcpy()

Posted May 1, 2014 18:32 UTC (Thu) by netghost (guest, #54048)
Parent article: The ups and downs of strlcpy()

You wrote such a long article to say the "up" and "down"s to justify "strlcpy()" not going into glibc, and the ONLY "down" side you points out in the article is "if you do not check the return value of strlcpy(), then you can lose data"? Sorry, this seems an very far-fetched argument to me, since how many C library functions can do EXACTLY what you want it to do WITHOUT checking return value and handling the error accordingly?


to post comments


Copyright © 2025, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds