HS>   cprintf() sends a formatted output STRAIGHT to the screen.
HS>   printf() sends a formatted output string to stdin.
   ... abrasives removed ...
HS>   the textcolor-family functions FAIL with printf()
HS>   (ANSI-C disallows it to do anything else other than send
HS>   to stdin).
HS>   That's why all these companies put in cprintf which
HS>   formats the str with ansi-colours. Like I said, if a
HS>   compiler doesn't have cprintf() then it contains an
HS>   equivalent which is most likely just printf().
   Beggin' your pardon m'lord, but Quick C, MS C, and Visual C++
   don't use colors in cprintf(). I don't mean to hype Mr.
   Gates, but Microsoft IS a bit in the mainstream.
   Any use of color and text positioning is highly dependent on
   platform and compiler. There is a small group of companies
   for whom it seems best to place all these functions within
   the console I/O library and attach them to cprintf(), which
   is a perfectly valid choice, in my meaningless opinion.
   Others, such as Microsoft, place these functions in the
   category of GRAPHICS manipulations, as opposed to TEXT,
   assuming, perhaps, that they are display related, and not
   text related, which also makes perfect sense. ( To me. )
   As a sidenote of some interest, anything sent to stdin
   would be likely to be coming from the keyboard, and not
   going out to the screen, lest it be via stdout. :)
   ( I know... but it was too easy to pass up! )
---
> ] Antimatter containment field failing. Dump standard .LIBs...
---
---------------