public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Paul Eggert <eggert@cs.ucla.edu>
To: "Alejandro Colomar (man-pages)" <alx.manpages@gmail.com>,
	mtk.manpages@gmail.com
Cc: linux-man@vger.kernel.org, libc-alpha@sourceware.org
Subject: Re: [PATCH] MAX.3, MIN.3: New page (and link page) to document MAX() and MIN()
Date: Wed, 12 May 2021 15:39:24 -0700	[thread overview]
Message-ID: <688adf87-e108-b4dd-66dd-ae9c4d7afdf8@cs.ucla.edu> (raw)
In-Reply-To: <b09b67a5-2006-62b7-13fc-1930b34e848b@gmail.com>

On 5/12/21 3:32 PM, Alejandro Colomar (man-pages) wrote:
> In which case they might not be evaluated at all?  I'm curious.
> Maybe if one of the arguments is literal NAN and the implementation
> raises an exception for it?

Or, one argument of MIN might be negative and the other might be 
unsigned short. In that case, the unsigned short argument need not be 
evaluated at all. Admittedly not something we'd be likely to optimize 
for, but the documentation shouldn't preclude such optimization.

  reply	other threads:[~2021-05-12 22:39 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-12 20:43 Alejandro Colomar
2021-05-12 20:56 ` [PATCH v2] " Alejandro Colomar
2021-05-12 20:59   ` Alejandro Colomar (man-pages)
2021-05-12 21:17 ` [PATCH] " Paul Eggert
2021-05-12 22:32   ` Alejandro Colomar (man-pages)
2021-05-12 22:39     ` Paul Eggert [this message]
2021-05-12 22:51       ` [PATCH v3] MAX.3, MIN.3: New pages " Alejandro Colomar
2021-06-12  8:35         ` Ping: " Alejandro Colomar (man-pages)
2021-06-20  2:39         ` Michael Kerrisk (man-pages)

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=688adf87-e108-b4dd-66dd-ae9c4d7afdf8@cs.ucla.edu \
    --to=eggert@cs.ucla.edu \
    --cc=alx.manpages@gmail.com \
    --cc=libc-alpha@sourceware.org \
    --cc=linux-man@vger.kernel.org \
    --cc=mtk.manpages@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).