From: a@9srv.net
To: 9fans@9fans.net
Subject: Re: [9fans] atol() bug
Date: Tue, 12 Mar 2013 17:05:56 -0400 [thread overview]
Message-ID: <762806b80f61840eb905ae8dc086fefa@9srv.net> (raw)
In-Reply-To: <20130312004009.0D736B834@mail.bitblocks.com>
// If the behavior is intended why not say so upfront and
// remove the BUGS section (or rename it to something else).
In Plan 9, the BUGS section is not really all about "bugs". This is
arguably unfortunate, but it's the way the system is. You might
check out
http://doc.cat-v.org/plan_9/misc/man_page_writing_howto
In particular, the section on BUGS says:
The BUGS section briefly lists shortcomings or other
‘‘gotchas’’ that the user should be aware of when using
the program. This is the place to mention things which
are unsatisfactory or tricky about the program, even if it
is not clear that they are bugs. Mentioning something in
a BUGS section does not imply a commitment to fix it.
Whenever you see the BUGS section in a Plan 9 man page,
mentally replace it with NOTE or BE CAREFUL ABOUT THIS BIT.
Changing the language in the actual description to be more
clear is largely an independent issue, and seems worthwhile.
// plan9 strings are not just ASCII anymore so the 'a' prefix
// makes less sense now!
More logically consistent, but I suspect originally this was a
concession to porting existing unix code, or a bad mental
habbit. At this point, it seems unreasonable to change.
Anthony
prev parent reply other threads:[~2013-03-12 21:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-11 22:09 Bakul Shah
2013-03-11 22:44 ` Steven Stallion
2013-03-11 22:55 ` Bakul Shah
2013-03-11 23:55 ` erik quanstrom
2013-03-12 0:25 ` Kurt H Maier
2013-03-12 0:40 ` Bakul Shah
2013-03-12 21:05 ` a [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=762806b80f61840eb905ae8dc086fefa@9srv.net \
--to=a@9srv.net \
--cc=9fans@9fans.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).