_print/_doprnt; curses on sys III

[rcc at imsvax.UUCP]

If you're adamant about speed, efficiency, etc., then do what ex does,
don't use stdio.  However, if you're going to use stdio, then you
should *not* use any undocumented/internal routines and claim that
the program is portable, even if you document the fact that you used
them.  Documenting that your program is dependent on multiplexed files
doesn't make it portable if a system doesn't have multiplexed
files (at least, not without some work).  Either include your own 
stdio in the program that works, or play by the rules.  Doing 
otherwise guarantees that your program will break.  The only 
question is when.
-- 

The preceding message was brought to you by --

		Ray Chen

UUCP:	umcp-cs!eneevax!imsvax!rcc  (NEW ADDRESS)
Voice:	(301)  984-8343
USnail:	Integrated Microcomputer Systems, Inc.
	Suite 400
	6100 Executive Blvd.
	Rockville, MD  20852