From: David Tolpin <dvd@davidashen.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] errstr(2)
Date: Thu, 25 Mar 2004 17:30:40 +0400 [thread overview]
Message-ID: <200403251330.i2PDUemX062614@adat.davidashen.net> (raw)
In-Reply-To: <2d02a062f561ff0711a63707cb49cb26@plan9.bell-labs.com>
> > My question was whether the code was right (in generrstr)
> > or accidental.
>
> In other words are we stupid or just incompetent?
I like the use of fixed-length buffer for error strings.
> You buffer len should be more determined by how long
> an error string you might consider useful.
Unless it is truncated by the kernel limit. So as long
as my buffer is not longer than ERRMAX, I'm on a safe
ground.
prev parent reply other threads:[~2004-03-25 13:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-25 6:43 David Tolpin
2004-03-25 6:51 ` Russ Cox
2004-03-25 7:08 ` David Tolpin
2004-03-25 12:33 ` David Presotto
2004-03-25 12:39 ` David Tolpin
2004-03-25 12:52 ` David Presotto
2004-03-25 12:57 ` lucio
2004-03-25 13:30 ` David Tolpin [this message]
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=200403251330.i2PDUemX062614@adat.davidashen.net \
--to=dvd@davidashen.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).