public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Michael Matz <matzmich@cs.tu-berlin.de>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: Frank Klemm <pfk@fuchs.offl.uni-jena.de>,
	Neil Booth <neil@daikokuya.demon.co.uk>, <gcc@gcc.gnu.org>
Subject: OT: Re: Proposal
Date: Sat, 29 Sep 2001 18:32:00 -0000	[thread overview]
Message-ID: <Pine.GSO.4.33.0109300238180.11225-100000@platon> (raw)
In-Reply-To: <20010929201517.A6942@nevyn.them.org>

Hi,

On Sat, 29 Sep 2001, Daniel Jacobowitz wrote:

> > > BILLION won't expand to what you think.  As for UK notation, I'm
> > > British and I can't think of the last time I've seen a billion have 12
> > > zeroes.  In fact, I think the only time it occurs is when people are
> > > comparing the claimed British and American forms :-)
> > >
> > A billion has no zeros: 1.e+12
>
> I think that what Neil meant is:
> % units billion
>         Definition: 1e9 = 1e+09

May be for your country.  E.g. germany has billion==1e12 (we have mi-,
bi-, tri-, quadri- and quinti- as first parts and -llion, and -lliard(e)
as second parts alternating.  I.e million==1e6, milliard(e)==1e9,
billion==1e12, billiarde=1e15 ... quintilliarde==1e33) for those, who are
interested ;-)

Given that a million is 1e6 in both countries, and a _bi_llion is somehow
two times a m(ono)illion, and 1e9 is neither the double of 1e6 nor has
twice as much zeros, whereas 1e12 has, I find our definition more logical.
But then again I may be biased ;)


Ciao,
Michael.

  reply	other threads:[~2001-09-29 18:32 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-15 11:45 Proposal Frank Klemm
2001-09-15 12:15 ` Proposal Gerald Pfeifer
2001-09-17 16:00 ` Proposal Neil Booth
2001-09-18  2:30   ` Proposal Joseph S. Myers
2001-09-18 10:21     ` Proposal Zack Weinberg
2001-09-18 11:14       ` Proposal Joseph S. Myers
2001-09-18 22:20         ` Proposal Zack Weinberg
2001-09-19  1:14           ` Proposal Joseph S. Myers
2001-09-18 12:23       ` Proposal Frank Klemm
2001-09-18 22:37         ` Proposal Zack Weinberg
2001-09-19  0:02           ` Proposal Neil Booth
2001-09-19  2:23             ` Proposal Tim Hollebeek
2001-09-19  2:41               ` Proposal Richard Earnshaw
2001-09-19 13:38         ` Proposal Joe Buck
2001-09-18 15:35       ` Proposal Robert Lipe
2001-09-18 16:59         ` Proposal Russ Allbery
2001-09-20 11:17           ` Proposal Kai Henningsen
2001-09-20 12:34             ` Proposal Russ Allbery
2001-09-18  9:48   ` Proposal Frank Klemm
2001-09-18 11:06     ` Proposal Neil Booth
2001-09-18 11:37     ` Proposal Kevin Handy
2001-09-18 15:48       ` Proposal Neil Booth
2001-09-18 15:55         ` Proposal Toon Moene
2001-09-27  5:39     ` Proposal Alexandre Oliva
2001-09-27  7:09       ` Proposal Frank Klemm
2001-09-27 16:22         ` Proposal Zack Weinberg
2001-09-29 15:45           ` Proposal Frank Klemm
2001-09-30  9:35             ` Proposal Zack Weinberg
2001-09-27 16:36         ` Proposal Neil Booth
2001-09-29 15:45           ` Proposal Frank Klemm
2001-09-29 17:22             ` Proposal Daniel Jacobowitz
2001-09-29 18:32               ` Michael Matz [this message]
2001-10-03  3:52         ` Proposal Fergus Henderson

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=Pine.GSO.4.33.0109300238180.11225-100000@platon \
    --to=matzmich@cs.tu-berlin.de \
    --cc=drow@mvista.com \
    --cc=gcc@gcc.gnu.org \
    --cc=neil@daikokuya.demon.co.uk \
    --cc=pfk@fuchs.offl.uni-jena.de \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).