From: "Paul A. Patience" <paul-a.patience@polymtl.ca>
To: 9fans@9fans.net
Subject: Re: [9fans] Bug in print(2) g verb
Date: Sun, 3 Mar 2013 12:46:48 -0500 [thread overview]
Message-ID: <7695c90c86f3e5fdb112868b1e13bf6f@yourdomain.dom> (raw)
I would also like it if %g acted the same in plan9
as everywhere else (printing 0.1 instead of .1 in
my example). That's also really easy to change.
It doesn't make sense for plan9port's %g to be
different from plan9, because now you cannot even
count on both prints to work the same way. Since
printf's %g works like plan9port right now, it
would make sense to change plan9's version.
I don't know the history behind %g's current
behaviour, however.
next reply other threads:[~2013-03-03 17:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-03 17:46 Paul A. Patience [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-02-28 2:49 Paul Patience
2013-03-01 0:08 ` Rob Pike
2013-03-01 2:57 ` Paul A. Patience
2013-03-01 4:54 ` Kurt H Maier
2013-03-01 15:30 ` Rob Pike
2013-03-01 15:58 ` Steve Simon
2013-03-01 17:38 ` Anthony Sorace
2013-03-01 22:53 ` Paul A. Patience
2013-03-03 17:33 ` erik quanstrom
2013-03-03 21:43 ` Richard Miller
2013-03-03 21:52 ` erik quanstrom
2013-03-03 17:57 ` Paul A. Patience
2013-03-03 18:26 ` 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=7695c90c86f3e5fdb112868b1e13bf6f@yourdomain.dom \
--to=paul-a.patience@polymtl.ca \
--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).