From: forsyth@caldo.demon.co.uk
To: 9fans@cse.psu.edu
Subject: Re: [9fans] snprint(), getfields() specification
Date: Thu, 10 May 2001 18:51:13 +0100 [thread overview]
Message-ID: <20010510175436.3410E19A1C@mail.cse.psu.edu> (raw)
>>If I had to pick one, I'd go for the length routine. If you really
>>care, always use it; if you never care, you want the actual number of
>>bytes and the snprint (not snprintf) result seems better.
would it not also avoid the proliferation of special interfaces for each possible
routine that does formatting (including the ones users invent)?
next reply other threads:[~2001-05-10 17:51 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-10 17:51 forsyth [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-05-10 17:56 rob pike
2001-05-10 17:40 erik quanstrom
2001-05-10 16:56 rob pike
[not found] <rob@plan9.bell-labs.com>
2001-05-10 14:59 ` rob pike
2001-05-10 16:42 ` Scott Schwartz
2001-05-10 18:13 ` Steve Kilbane
2001-05-10 21:38 ` Boyd Roberts
2001-05-11 6:51 ` Steve Kilbane
2001-05-10 14:30 rob pike
2001-05-11 8:33 ` Douglas A. Gwyn
2001-05-14 8:36 ` David Rubin
2001-05-10 13:56 rob pike
2001-05-10 14:25 ` Greg Hudson
2001-05-10 14:44 ` William Josephson
2001-05-10 5:11 Scott Schwartz
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=20010510175436.3410E19A1C@mail.cse.psu.edu \
--to=forsyth@caldo.demon.co.uk \
--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).