public inbox for gsl-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Brian Gough <bjg@gnu.org>
To: Thanh Vo <vo@ucdavis.edu>
Cc: gsl-discuss@sourceware.org, bug-gsl@gnu.org,
	"Earl T. Barr" <etbarr@ucdavis.edu>
Subject: Re: [Bug-gsl] Potential Bugs?
Date: Tue, 17 Aug 2010 20:47:00 -0000	[thread overview]
Message-ID: <43k4np6k66.wl%bjg@gnu.org> (raw)
In-Reply-To: <43mxsl6klg.wl%bjg@gnu.org>

At Tue, 17 Aug 2010 21:38:19 +0100,
Brian Gough wrote:
> The overflow exception is a valid warning.  It's also a bug in the
> sense that it is avoidable (although the end result is correct, z=-1
> since 1/inf=0).  It would be better written as (32/y)/y.

Of course, apart from the extra factor of 2^5 that gives an underflow
instead but it's probably preferable to an overflow.

      reply	other threads:[~2010-08-17 20:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <AANLkTinA0Bo1tS-AuqeE62O=SqcDSMffHWKbxh5G4a1V@mail.gmail.com>
2010-08-17 20:38 ` Brian Gough
2010-08-17 20:47   ` Brian Gough [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=43k4np6k66.wl%bjg@gnu.org \
    --to=bjg@gnu.org \
    --cc=bug-gsl@gnu.org \
    --cc=etbarr@ucdavis.edu \
    --cc=gsl-discuss@sourceware.org \
    --cc=vo@ucdavis.edu \
    /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).