unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Andy Wingo <wingo@pobox.com>
To: Matt Wette <matt.wette@gmail.com>
Cc: guile-devel@gnu.org
Subject: Re: GNU Guile 2.1.5 released (beta)
Date: Sun, 08 Jan 2017 23:54:18 +0100	[thread overview]
Message-ID: <87shotb1t1.fsf@pobox.com> (raw)
In-Reply-To: <17F492ED-FA6D-42AB-92C3-D746FC9F6D1B@gmail.com> (Matt Wette's message of "Sun, 11 Dec 2016 17:25:19 -0800")

Just a note -- your work here is really appreciated!  I know I'm a
verrrry async with patches but your work is indeed appreciated,
especially in the run-up to a 2.2.0 when I hope to have handled most all
these bugs.

Andy

On Mon 12 Dec 2016 02:25, Matt Wette <matt.wette@gmail.com> writes:

>  On Dec 11, 2016, at 12:35 PM, Matt Wette <matt.wette@gmail.com> wrote:
>
>  With patches I can compile and run “make check”. But now I have one failure:t tests/numbers.test line 1663: (“#i1@-0” 1.0 -0.0). 
>
>  This wants the following to produce #t, but it does not:
>
>  scheme@(guile-user)> (define z (string->number "#i1@-0"))
>  scheme@(guile-user)> (eqv? (imag-part z) -0.0)
>  $7 = #f
>
> Sorry to keep posting on this. I will stop soon. I seem to get different problems every time I build 2.1.5 on my Mac. I am using some different config options (e.g., with and without
> —disable-shared) and different compilers. The above issue does not show up with the current build. Note the following separate builds that give different values for the above:
>
> mwette$ pwd
> /Users/mwette/proj/scheme/guile/guile-2.1.5
> mwette$ meta/guile -c '(display (eqv? (imag-part (string->number "#i1@-0")) -0.0))'
> #f
>
> mwette$ pwd
> /Users/mwette/proj/scheme/guile/guile-2.1.5-2
> mwette$ meta/guile -c '(display (eqv? (imag-part (string->number "#i1@-0")) -0.0))'
> #t



  parent reply	other threads:[~2017-01-08 22:54 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-07 19:55 GNU Guile 2.1.5 released (beta) Andy Wingo
2016-12-09 15:28 ` Matt Wette
2016-12-09 17:25   ` Christopher Allan Webber
2016-12-10 13:16   ` Matt Wette
2016-12-11 14:52     ` Matt Wette
2016-12-11 15:42     ` Matt Wette
2017-01-08 22:50       ` Andy Wingo
2016-12-11 15:17   ` Matt Wette
2016-12-12 13:45     ` Matt Wette
2016-12-12 20:46       ` Matt Wette
2016-12-13  1:24         ` dsmich
2016-12-13 21:26           ` Freja Nordsiek
2016-12-16 13:50             ` Matt Wette
2016-12-16 14:05               ` Matt Wette
2016-12-17  2:03                 ` Christopher Allan Webber
2016-12-17  3:07                   ` Matt Wette
2016-12-11 20:35 ` Matt Wette
2016-12-12  1:25   ` Matt Wette
2016-12-12 11:14     ` tomas
2017-01-08 22:54     ` Andy Wingo [this message]
2017-01-09  0:13       ` Matt Wette
2016-12-20 15:00 ` Matt Wette
2016-12-20 22:58   ` Matt Wette
2017-01-08 23:01     ` Andy Wingo
2017-01-08 23:28       ` Matt Wette
     [not found] <mailman.109.1481389218.15985.guile-devel@gnu.org>
2016-12-10 17:11 ` Daniel Llorens
2016-12-11  0:42   ` Matt Wette
2016-12-29 19:38     ` Matt Wette

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/guile/

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

  git send-email \
    --in-reply-to=87shotb1t1.fsf@pobox.com \
    --to=wingo@pobox.com \
    --cc=guile-devel@gnu.org \
    --cc=matt.wette@gmail.com \
    /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).