ML>     IBM C Set++ has the same  non-ANSI I/O functions as all
ML> other C compilers I am familiar with.  However, C Set++ is a little more
ML> ANSI-compliant than many other compilers.  In accordance with the

More ANSI-compliant than which compilers, e.g.?  There's very little
sign of non-ISO compliance in the compilers that I use, and that's
a fair range.

ML> standard, non-ANSI library functions have an underscore as the leading
ML> symbol in the function name.

There is no requirement for this, unless they interfere with the
namespace of the resultant executable.  You will find that with
a compiler such as Borland, which has a kbhit(), you can create
your own function called kbhit(), and it will not clash with the
one that Borland provide.  You are free to be blissfully unaware
that they provide such a function as an extension, and so long as
YOU follow the ISO standard, your program will compile, link and
run properly.

BFN.  Paul.
@EOT:

---