Ive got errors compiling code that uses certain string functions. Why?
{AJ} glibc 2.1 has special string functions that are faster than the normal library functions. Some of the functions are additionally implemented as inline functions and others as macros. This might lead to problems with existing codes but it is explicitly allowed by ISO C. The optimized string functions are only used when compiling with optimizations (-O1 or higher). The behavior can be changed with two feature macros: • __NO_STRING_INLINES: Don’t do any string optimizations. • __USE_STRING_INLINES: Use assembly language inline functions (might increase code size dramatically). Since some of these string functions are now additionally defined as macros, code like “char *strncpy();” doesn’t work anymore (and is unnecessary, since
Related Questions
- My property does not currently meet building codes - to bring it up to code may mean that certain historic features are sacrificed. Would the project still qualify?
- How do I fix link errors about missing functions when compiling DLLs on Windows?
- Ive got errors compiling code that uses certain string functions. Why?