9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Richard Miller <9fans@hamnavoe.com>
To: 9fans@9fans.net
Subject: Re: [9fans] Bug in print(2) g verb
Date: Sun,  3 Mar 2013 21:43:39 +0000	[thread overview]
Message-ID: <f999c4e25337a1ff8db31e48a46df905@hamnavoe.com> (raw)
In-Reply-To: <71728259d50eb69a37b67beb0ff72e37@kw.quanstro.net>

> /sys/src/cmd/hoc/code.c:586: 	print("%.12g\n", d.val);

Conceivably changing this could break somebody's rc script which depends on
hoc leaving out the leading zero.  But unlikely (one hopes) that someone with
the taste to use Plan 9 would write anything so fragile...

I vote we converge with plan9port's behaviour on this.




  reply	other threads:[~2013-03-03 21:43 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
2013-03-03 21:52             ` erik quanstrom
2013-03-03 18:54         ` [9fans] doing a native awk port (was Re: Bug in print(2) g verb) arnold
2013-03-03 19:04           ` Paul A. Patience
2013-03-03 19:08             ` erik quanstrom
2013-03-03 19:11               ` Kurt H Maier
2013-03-03 19:18                 ` erik quanstrom
2013-03-03 19:28                   ` Kurt H Maier
2013-03-03 19:31                     ` erik quanstrom
2013-03-03 19:35                       ` Kurt H Maier
2013-03-04  0:10                       ` Dan Cross
2013-03-04  0:39                         ` Kurt H Maier
2013-03-03 19:07           ` erik quanstrom
2013-03-03 21:29             ` Richard Miller
2013-03-03 21:38               ` erik quanstrom
2013-03-03 17:57       ` [9fans] Bug in print(2) g verb Paul A. Patience
2013-03-03 18:26         ` erik quanstrom
2013-03-03 17:46 Paul A. Patience

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=f999c4e25337a1ff8db31e48a46df905@hamnavoe.com \
    --to=9fans@hamnavoe.com \
    --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).