Why are some ANSI/ISO Standard library functions showing up as undefined, even though Ive got an ANSI compiler?
It’s possible to have a compiler available which accepts ANSI syntax, but not to have ANSI-compatible header files or run-time libraries installed. (In fact, this situation is rather common when using a non-vendor-supplied compiler such as gcc.) See also questions 11.29a, 13.25, and 13.26. comp.lang.c FAQ list ยท Question 11.31 Q: Does anyone have a tool for converting old-style C programs to ANSI C, or vice versa, or for automatically generating prototypes? A: Two programs, protoize and unprotoize, convert back and forth between prototyped and “old style” function definitions and declarations. (These programs do not handle full-blown translation between “Classic” C and ANSI C.) These programs are part of the FSF’s GNU C compiler distribution; see question 18.3. The unproto program (/pub/unix/unproto5.shar.Z on ftp.win.tue.nl) is a filter which sits between the preprocessor and the next compiler pass, converting most of ANSI C to traditional C on-the-fly. The GNU GhostScript package
Related Questions
- Why are some ANSI/ISO Standard library functions showing up as undefined, even though Ive got an ANSI compiler?
- compiler can accelerate practically any ANSI C code, can it accelerate C library functions like printf()?
- Does the 2007 revision of the ANSI Z535.4 Standard incorporate ISO safety label formats?
