From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@cse.psu.edu, Charles Forsyth <forsyth@terzarima.net>
Subject: Re: [9fans] warning of putchar
Date: Sat, 14 Jan 2006 06:33:32 -0600 [thread overview]
Message-ID: <20060114123332.7808B114987@dexter-peak.quanstro.net> (raw)
In-Reply-To: <9a066da3dec0d1f7e7a26e51d50154ce@terzarima.net>
i'm only getting half of this conversation on the list.
does this have anything to do with the putchar email
that quoted an email that wasn't on the list?
- erik
Charles Forsyth <forsyth@terzarima.net> writes
|
| even more amusing, try to suppress them by including an ugly
| lint-style cast to void, and you'll get a further such diagnostic
| (and serve you right for adding clutter)!
|
| more helpfully, if you're writing a new program for Plan 9,
| use bio(2) instead
next prev parent reply other threads:[~2006-01-14 12:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-14 9:07 党立斌
2006-01-14 10:40 ` Bruce Ellis
2006-01-14 12:18 ` Charles Forsyth
2006-01-14 12:33 ` erik quanstrom [this message]
2006-01-14 18:25 ` Russ Cox
2006-01-14 21:29 ` erik quanstrom
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=20060114123332.7808B114987@dexter-peak.quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@cse.psu.edu \
--cc=forsyth@terzarima.net \
/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).