From: William Case <billlinux@rogers.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Tutorial question re conventions or usage ??
Date: Tue, 01 May 2007 15:51:30 -0400 [thread overview]
Message-ID: <1178049090.3157.43.camel@CASE> (raw)
In-Reply-To: <u3b2gwdar.fsf@gnu.org>
Thanks Eli
On Tue, 2007-05-01 at 22:31 +0300, Eli Zaretskii wrote:
> > From: William Case <billlinux@rogers.com>
> > Date: Tue, 01 May 2007 13:44:18 -0400
> >
[snip]
> I think it's more likely that the author wanted to avoid
> floating-point arithmetics, and also avoid overflow (as the comment
> says). Interpreting the argument as percentage would require
> multiplication by 100, which would exacerbate the integer overflow
> problem.
>
> Just a guess.
>
Just wanted make sure I understood the problem he was trying to solve.
--
Regards Bill
prev parent reply other threads:[~2007-05-01 19:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-01 17:44 Tutorial question re conventions or usage ?? William Case
2007-05-01 19:31 ` Eli Zaretskii
2007-05-01 19:51 ` William Case [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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1178049090.3157.43.camel@CASE \
--to=billlinux@rogers.com \
--cc=eliz@gnu.org \
--cc=help-gnu-emacs@gnu.org \
/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).