From: Random832 <random832@fastmail.com>
To: tuhs@minnie.tuhs.org
Subject: Re: [TUHS] Any Good dmr Anecdotes?
Date: Mon, 09 Jul 2018 12:30:39 -0400 [thread overview]
Message-ID: <1531153839.3991054.1434840984.210C4B3F@webmail.messagingengine.com> (raw)
In-Reply-To: <009101d4112f$8bb30f50$a3192df0$@ronnatalie.com>
On Sun, Jul 1, 2018, at 07:34, ron@ronnatalie.com wrote:
> The bigger issue with the early printf is it just called putchar and
> putchar only output to stdout or what ever the global fout variable was
> set to.
> There was a comment in the manual that the fout concept was kludgy.
V6 'iolib' printf has an interesting approach to fixing this:
If the first argument was 0 through 9, it was taken to be a file descriptor, and the second argument was the format string. If it was -1, the second argument was the output string (as for later sprintf), and the third was the format string. Otherwise, the first argument was the format string.
(I'm curious as to how much "iolib" was actually used, since it doesn't appear to have been included by default - there was a different printf routine in libc)
next prev parent reply other threads:[~2018-07-09 16:37 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-29 7:53 Warren Toomey
2018-06-29 10:53 ` ches@Cheswick.com
2018-06-29 12:51 ` John P. Linderman
2018-06-30 0:50 ` Steve Johnson
2018-06-30 11:44 ` Arrigo Triulzi
2018-06-30 22:42 ` Arthur Krewat
2018-06-30 23:29 ` Arrigo Triulzi
2018-07-01 4:17 ` Larry McVoy
2018-07-01 11:42 ` ron
2018-07-01 5:29 ` Dave Horsfall
2018-07-01 8:28 ` Arrigo Triulzi
2018-07-01 11:34 ` ron
2018-07-09 16:30 ` Random832 [this message]
2018-07-09 17:13 ` Clem Cole
2018-07-10 5:54 ` arnold
2018-07-10 6:09 ` George Michaelson
2018-07-10 7:19 ` arnold
2018-07-11 0:20 ` Noel Hunt
2018-07-11 1:31 ` Larry McVoy
2018-07-11 1:37 ` George Michaelson
2018-07-11 1:37 ` ron minnich
2018-07-11 3:12 ` Larry McVoy
2018-07-11 3:34 ` [TUHS] getopt (was " Bakul Shah
2018-07-13 9:08 ` [TUHS] " ches@Cheswick.com
2018-07-13 14:10 ` ron
2018-07-10 14:10 ` Clem Cole
2018-07-03 17:34 ` Perry E. Metzger
2018-06-29 23:55 ` Dave Horsfall
2018-06-30 0:06 ` Greg 'groggy' Lehey
2018-06-30 14:20 ` John P. Linderman
2018-06-30 1:31 Larry McVoy
2018-06-30 1:45 ` Jon Forrest
2018-06-30 18:43 ` Steve Johnson
2018-07-01 16:35 Norman Wilson
2018-07-02 19:55 Paul Ruizendaal
2018-07-03 7:27 arnold
2018-07-18 9:42 Hendrik Jan Thomassen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1531153839.3991054.1434840984.210C4B3F@webmail.messagingengine.com \
--to=random832@fastmail.com \
--cc=tuhs@minnie.tuhs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).