On Sat, 25 Sep 2004 16:18:24 +0200 (W. Europe Daylight Time) Frans Meijer <[EMAIL
PROTECTED]> wrote:
FM> A number of standard C-lib symbols were referenced by their underscored
FM> name, such as _stricmp. I edited these to their regular names. Was there
FM> a specific reason to use these versions?
These are not standard C library functions, they're standard Unix ones
(for this one) or POSIX ones (for _open(), _read(), ...). For this reason,
i.e. to avoid confusion with ANSI C functions, Microsoft compiler headers
define them with underscore prefix. The underscore-less versions are only
defined ("for compatibliity", according to a comment in the headers) if
__STDC__ is not set but it would be a bad idea to unset it.
The standard solution is to have something like
#ifdef _MSC_VER
#define open _open
...
#define stricmp _stricmp
#endif
in some header when one still wants to use these functions.
Regards,
VZ
