Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site ur-tut.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!mhuxr!mhuxt!houxm!vax135!cornell!bullwinkle!rochester!ur-tut!tfra
From: tfra@ur-tut.UUCP (Thomas Fravenhofer)
Newsgroups: net.unix,net.unix-wizards
Subject: "_doprnt" results
Message-ID: <301@ur-tut.UUCP>
Date: Wed, 18-Dec-85 21:44:35 EST
Article-I.D.: ur-tut.301
Posted: Wed Dec 18 21:44:35 1985
Date-Received: Fri, 20-Dec-85 04:56:25 EST
References: <>
Reply-To: tfra@ur-tut.UUCP (Thomas Fravenhofer)
Organization: Univ. of Rochester Computing Center
Lines: 22
Keywords: _doprnt _dontprn _willprnt _wontprnt
Xref: watmath net.unix:6678 net.unix-wizards:16171

[Virgin line sacrified to the God of Line Eating]

I got QUITE a bit of mail on my request for what _doprnt, so I thought I'd
summarize the results rather than send individual replies.  Here goes:

_doprnt is a routine which does not exist on all unix systems.  It basically
does all the work of printf, fprintf, and sprintf in formatting the text.

A companion routine of _doprnt is _strout, which appears to be an output
routine (sending output to either standard output, a specific file, or a
character string).

Thanks to all who answered my question.  For those who wonder what my problem
was, it turned out not to be bad parameters sent to anything, but rather a
poor linker.  It seems one of the modules I was compiling contained its own
version of _strout, but the linker was still pulling in the version of
_strout from libc.  When I later tried to execute _strout, it didn't know
which one to call, so it went to never-never land.

- Tom Frauenhofer

"A closed mouth gathers no feet" - Mark Twain