Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.1a 12/4/83; site rlgvax.UUCP Path: utzoo!watmath!clyde!floyd!vax135!houxz!houxm!ihnp4!zehntel!hplabs!hao!seismo!rlgvax!guy From: guy@rlgvax.UUCP (Guy Harris) Newsgroups: net.unix-wizards Subject: Re: _print/_doprnt; curses on sys III Message-ID: <2036@rlgvax.UUCP> Date: Tue, 26-Jun-84 01:36:51 EDT Article-I.D.: rlgvax.2036 Posted: Tue Jun 26 01:36:51 1984 Date-Received: Fri, 22-Jun-84 07:32:18 EDT References: <948@sri-arpa.UUCP> Organization: CCI Office Systems Group, Reston, VA Lines: 15 > It is standard System III. AT&T finally wised up to how much software > broke when they took _doprnt away, and made it come back in System V. > Not that this helps you any, but..... Well, I looked, and "_doprnt" is back; in S5R2, they also provide the "vprintf", "vfprintf", and "vsprintf" interfaces that were in S3 as distributed (and which can be used instead of "_doprnt"), but were ripped out of S5. "_doprnt" is, alas, not in every implementation of standard I/O, so software which uses it will still break under some implementations. Alas, there is no portable way to write routines which take "printf"-like call interfaces; neither "v*printf" nor "_doprnt" are guaranteed to be there ("v*printf" were in the distributed S3, but not documented). Guy Harris {seismo,ihnp4,allegra}!rlgvax!guy