From: Charlie Brady <charlieb-supervision@budge.apana.org.au>
Cc: supervision@list.skarnet.org
Subject: Re: problems with QMAILQUEUE and reading stdin
Date: Mon, 29 May 2006 10:38:19 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.61.0605291036240.24384@e-smith.charlieb.ott.istop.com> (raw)
In-Reply-To: <20060529133744.GB15937@run.galis.org>
On Mon, 29 May 2006, George Georgalis wrote:
> I'd prefer to specify stdin as an argument, I'd like to retain
> that style for helping people (including myself) interpret the
> code.
Why? If someone is reading code and they don't know that programs which
read stdin by default actually read stdin if you don't do anything
special, then they can't interpret much code at all, can they?
Add a comment about reading stdin if you really think you need it.
next prev parent reply other threads:[~2006-05-29 14:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-29 1:58 George Georgalis
2006-05-29 5:23 ` B S Srinidhi
2006-05-29 12:11 ` Charlie Brady
2006-05-29 12:19 ` B S Srinidhi
2006-05-29 13:37 ` George Georgalis
2006-05-29 14:38 ` Charlie Brady [this message]
2006-05-29 15:49 ` George Georgalis
2006-05-29 15:56 ` Charlie Brady
2006-05-29 20:48 ` George Georgalis
2006-05-29 13:59 ` Charlie Brady
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=Pine.LNX.4.61.0605291036240.24384@e-smith.charlieb.ott.istop.com \
--to=charlieb-supervision@budge.apana.org.au \
--cc=supervision@list.skarnet.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).