On 5/22/07, Michael L Torrie <[EMAIL PROTECTED]> wrote: > Not even strcmp should be used anymore since it can't support non-ANSI > encodings. Consider it highly deprecated. It was nice when it was > actually useful, since it was a portable function that always worked. > That's the reason you don't ever want to re-implement a library > function, generic trade-offs notwithstanding. Fortunately new libraries > are out now on all platforms to address character set issues.
Not to mention that some of the older functions like strcmp and strcpy are unsafe. Both of these allow for buffer overflow. Valgrind now lists strcmp and strcpy as memory errors and unsafe operations due to this possibility. -- Alex Esplin -------------------- BYU Unix Users Group http://uug.byu.edu/ The opinions expressed in this message are the responsibility of their author. They are not endorsed by BYU, the BYU CS Department or BYU-UUG. ___________________________________________________________________ List Info: http://uug.byu.edu/cgi-bin/mailman/listinfo/uug-list
