From: Matthias Kopfermann <matthi@infodrom.north.de>
To: Peter Stephenson <pws@csr.com>
Cc: zsh-workers@sunsite.dk
Subject: Re: print and floating point output
Date: Tue, 11 May 2004 15:08:57 +0200 [thread overview]
Message-ID: <20040511130857.GA24416@finlandia.infodrom.north.de> (raw)
On Tue, May 11, 2004 at 01:01:06PM +0100, Peter Stephenson wrote:
> Well, the alternative is silently censoring decimal places, many of
> which may be valid. If you want something smart to guess how many
> places are valid, you need to write it.
So you think that ruby, perl and python censor output?
I think that's just useful and uses the principle of least
surprise.
> typeset -E 8 var
>
> then
>
> (( var = 2.8 * 16.0 ))
> print $var
>
> for a given number of decimal places. Or use printf, which does it's
> own conversion:
I know about printf and typeset already. I just thought that
perl, ruby and python have good points in their decision,
too. :)
And what's the way of using typeset with something like
print $((2.8*16.0)) ?
plus, bc does it that way, too.
and i don't think that bc does censor my output at all.
Well, to a point there always is censoring with floating
point, ack!
>
> % printf "%f\n" $((2.8*16.0))
> 44.800000
Why is that no censoring then?
>
> If you are doing serious floating point work, unfortunately you need to
> understand something about rounding errors, which are a tricky and
> ever-present feature.
I learned that here.
Matthias
next reply other threads:[~2004-05-11 13:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-11 13:08 Matthias Kopfermann [this message]
2004-05-11 13:18 ` Peter Stephenson
2004-05-11 14:13 ` Matthias Kopfermann
2004-05-11 15:07 ` Peter Stephenson
-- strict thread matches above, loose matches on Subject: below --
2004-05-11 11:43 Matthias Kopfermann
2004-05-11 11:57 ` DervishD
2004-05-11 12:01 ` Peter Stephenson
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=20040511130857.GA24416@finlandia.infodrom.north.de \
--to=matthi@infodrom.north.de \
--cc=pws@csr.com \
--cc=zsh-workers@sunsite.dk \
/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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
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).