all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Kaelyn <kaelyn.alexi@protonmail.com>
To: Felix Lechner <felix.lechner@lease-up.com>
Cc: Andreas Enge <andreas@enge.fr>, guix-devel@gnu.org
Subject: Re: Procps in core-updates
Date: Sun, 19 Mar 2023 19:22:54 +0000	[thread overview]
Message-ID: <7qnn6PFyX-InJ5znfYbddEfgm0MbaZVnjTQ4Q1mj9wj5lY-8khBOjAfERvHVRxAIp__NEpo_GeQnYEkNDc4S_YxJXpAv3nQR3tXFVbjh7S0=@protonmail.com> (raw)
In-Reply-To: <CAFHYt55+ePPtB3DDL33iBiSc2kHzbF3xFk+Ht+sbDaxJJuResg@mail.gmail.com>

Hi Felix,

------- Original Message -------
On Sunday, March 19th, 2023 at 5:49 PM, Felix Lechner via "Development of GNU Guix and the GNU System distribution." <guix-devel@gnu.org> wrote:


> 
> 
> Hi Andreas,
> 
> On Sat, Mar 18, 2023 at 5:33 AM Andreas Enge andreas@enge.fr wrote:
> 
> > FAIL: strtod_nol_or_err("123") != 123.000000
> 
> 
> Can you multiply by "1.0" to force a floating-point comparison, or
> round the other side to the nearest int?

Judging from the function name ("strtod_nol_or_err", which seems in line with the standard "strtof"/"strtod"/"strtold" conversion functions), the function returns a double value. Depending on the specific code, it could be encountering inconsistencies comparing a double to a float (non-double) constant due to the difference in types' precision.

Cheers,
Kaelyn

> 
> Kind regards
> Felix


      reply	other threads:[~2023-03-19 19:23 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-18 12:32 Procps in core-updates Andreas Enge
2023-03-18 17:38 ` Leo Famulari
2023-03-18 17:44   ` Andreas Enge
2023-03-19 17:36 ` Michael Schierl
2023-03-20 14:54   ` Andreas Enge
2023-03-20 20:02     ` Michael Schierl
2023-03-20 21:25       ` Andreas Enge
2023-03-19 17:49 ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2023-03-19 19:22   ` Kaelyn [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='7qnn6PFyX-InJ5znfYbddEfgm0MbaZVnjTQ4Q1mj9wj5lY-8khBOjAfERvHVRxAIp__NEpo_GeQnYEkNDc4S_YxJXpAv3nQR3tXFVbjh7S0=@protonmail.com' \
    --to=kaelyn.alexi@protonmail.com \
    --cc=andreas@enge.fr \
    --cc=felix.lechner@lease-up.com \
    --cc=guix-devel@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. 
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.