On 3/5/07, jerry gay <[EMAIL PROTECTED]> wrote:
On 3/5/07, Kevin Tew <[EMAIL PROTECTED]> wrote: > Defining _CRT_SECURE_NO_DEPRECATE on the compiler command line is > probably the right solution here. > Kevin > i disagree. the reason C<strdup>, C<strnicmp> and C<stricmp> were deprecated is because they're non-ansi. therefore, microsoft renamed it to C<_strdup>. since we've pledged ansi (aka c89) c compliance, we should be following a similar path. instead of disabling the *valid* compiler warning, i suggest that either we modify our coding standard to allow C<strdup>, or we rename all usage to C<_strdup> and #define as appropriate for each compiler.
Moreover, strdup was not deprecated without a reason; strdup is claimed to be unsafe. It might be a good idea to accept this piece of advice, and use _strdup and friends. kjs
