From: Dmitry Alexandrov <dag@gnui.org>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: 42644@debbugs.gnu.org
Subject: bug#42644: 28.0.50; Please let max and min accept zero arguments
Date: Mon, 03 Aug 2020 20:11:25 +0300 [thread overview]
Message-ID: <zh7bejsy.dag@gnui.org> (raw)
In-Reply-To: <87d048wkf8.fsf@web.de> (Michael Heerdegen's message of "Mon, 03 Aug 2020 04:08:27 +0200")
[-- Attachment #1: Type: text/plain, Size: 1034 bytes --]
Michael Heerdegen <michael_heerdegen@web.de> wrote:
> Dmitry Alexandrov <dag@gnui.org> writes:
>
>> What reader syntax would you prefer?
>
> I'm not criticizing the current syntax for the infinities. It's just hard to remember them.
???
>> As for that regard, whatʼs wrong with, (/ +1.0 0) and (/ -1.0 0)?
>
> Wow, that doesn't error?
Thankfully, no. So third-parties do not have to invent another numbers, like in some other languages:
>>> 1 / 0.0
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
ZeroDivisionError: float division by zero
>>> import numpy
>>> 1 / numpy.float64(0.0)
inf
> It's hard to find a mathematical interpretation in which this makes any sense.
Dunno. It makes perfect natural sense to me. Perhaps, mathematics is too mind-warping. :-)
Also, Iʼd better emphasised zero, not numerator, with explicit flonum notation. I hope, writing the same thing another way would help to realise how obvious it is:
(/ +1 0.0) ; ⇒ 1.0e+INF
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]
next prev parent reply other threads:[~2020-08-03 17:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-01 6:30 bug#42644: 28.0.50; Please let max and min accept zero arguments Michael Heerdegen
2020-08-01 10:02 ` Stefan Kangas
2020-08-01 10:21 ` Andy Moreton
2020-08-01 10:21 ` Mattias Engdegård
2020-08-01 16:31 ` Drew Adams
2020-08-01 23:34 ` Michael Heerdegen
2020-08-02 4:02 ` Lars Ingebrigtsen
2020-08-02 6:43 ` Dmitry Alexandrov
2020-08-03 2:08 ` Michael Heerdegen
2020-08-03 11:05 ` Stefan Kangas
2020-08-03 17:11 ` Dmitry Alexandrov [this message]
2022-02-12 8:09 ` Lars Ingebrigtsen
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=zh7bejsy.dag@gnui.org \
--to=dag@gnui.org \
--cc=42644@debbugs.gnu.org \
--cc=michael_heerdegen@web.de \
/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.savannah.gnu.org/cgit/emacs.git
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).