Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.1 6/24/83; site imsvax.UUCP Path: utzoo!linus!philabs!cmcl2!seismo!rlgvax!cvl!elsie!imsvax!rcc From: rcc@imsvax.UUCP Newsgroups: net.unix-wizards Subject: Re: _print/_doprnt; curses on sys III Message-ID: <196@imsvax.UUCP> Date: Wed, 20-Jun-84 17:53:46 EDT Article-I.D.: imsvax.196 Posted: Wed Jun 20 17:53:46 1984 Date-Received: Fri, 22-Jun-84 11:05:55 EDT References: <948@sri-arpa.UUCP> <2036@rlgvax.UUCP> Organization: IMS Inc, Rockville MD Lines: 22 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