From: "Boyd Roberts" <boyd@fr.inter.net>
To: <9fans@cse.psu.edu>
Subject: Re: [9fans] thread
Date: Fri, 6 Jul 2001 20:24:33 +0200 [thread overview]
Message-ID: <025701c10648$e80c80b0$c0b7c6d4@SOMA> (raw)
In-Reply-To: <200107061441.KAA25020@augusta.math.psu.edu>
> However, Dennis clarified how it ...
he did, but do not forget that he said that printf
is varadic.
do not forget either that using %d with pointers (to int
or anything thing else) is fraught with peril.
next prev parent reply other threads:[~2001-07-06 18:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-06 4:15 arisawa
2001-07-06 14:41 ` Dan Cross
2001-07-06 18:24 ` Boyd Roberts [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-07-06 5:55 dmr
2001-07-06 16:54 ` Digby Tarvin
2001-07-09 8:33 ` Douglas A. Gwyn
2001-07-09 11:46 ` Digby Tarvin
2001-07-09 17:03 ` Dan Cross
2001-07-09 11:49 ` Boyd Roberts
2001-07-06 1:02 rob pike
2001-07-06 0:50 arisawa
2001-07-06 2:05 ` Dan Cross
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='025701c10648$e80c80b0$c0b7c6d4@SOMA' \
--to=boyd@fr.inter.net \
--cc=9fans@cse.psu.edu \
/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).