From: Vincent Lefevre <vincent@vinc17.net>
To: Alejandro Colomar <alx@kernel.org>
Cc: linux-man@vger.kernel.org
Subject: Re: [PATCH] man/: Replaced reserved exp identifier
Date: Thu, 3 Jul 2025 04:34:51 +0200 [thread overview]
Message-ID: <20250703023451.GJ12583@qaa.vinc17.org> (raw)
In-Reply-To: <hg3uyynudxq2bm2cl2spcm6nshjewbcoaxoxjzamtuzevcwyyw@d2ituhdydzmw>
On 2025-07-02 16:41:28 +0200, Alejandro Colomar wrote:
> On Wed, Jul 02, 2025 at 11:25:16AM +0200, Vincent Lefevre wrote:
[...]
> > --- a/man/man2/timerfd_create.2
> > +++ b/man/man2/timerfd_create.2
> > @@ -639,12 +639,12 @@ main(int argc, char *argv[])
> > {
> > int fd;
> > ssize_t s;
> > - uint64_t exp, tot_exp, max_exp;
> > + uint64_t ex, tot_ex, max_ex;
>
> How about using 'to' for timeout? Do you think it makes sense?
As described by the man page, this is more a timer expiration
(many occurrences of words starting with "expir") than a timeout
(a single occurrence - shouldn't this be "expiration time"?).
So, for these 3 variables, instead of "exp", perhaps "te" for
"timer expiration"?
> > struct timespec now;
> > struct itimerspec new_value;
> > \&
> > if (argc != 2 && argc != 4) {
> > - fprintf(stderr, "%s init\-secs [interval\-secs max\-exp]\[rs]n",
> > + fprintf(stderr, "%s init\-secs [interval\-secs max\-ex]\[rs]n",
>
> And here saying max\-timeout.
One could actually let max\-exp. Or say max\-timer\-exp (the line
would not be too large).
[...]
> > --- a/man/man3/frexp.3
> > +++ b/man/man3/frexp.3
> > @@ -14,9 +14,9 @@ Math library
> > .nf
> > .B #include <math.h>
> > .P
> > -.BI "double frexp(double " x ", int *" exp );
> > -.BI "float frexpf(float " x ", int *" exp );
> > -.BI "long double frexpl(long double " x ", int *" exp );
> > +.BI "double frexp(double " x ", int *" p );
> > +.BI "float frexpf(float " x ", int *" p );
> > +.BI "long double frexpl(long double " x ", int *" p );
>
> Here I think I'd use 'e' for exponent. What do you think?
One could do that (this was more or less my initial idea,
and I'm wondering why the committee chose p).
BTW, for frexp, this is a pointer, while for ldexp, this is
an integer. So, should there be a difference (e.g. pe for
the pointer to the exponent, and e for the exponent)?
--
Vincent Lefèvre <vincent@vinc17.net> - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / Pascaline project (LIP, ENS-Lyon)
next prev parent reply other threads:[~2025-07-03 2:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-02 9:25 [PATCH] man/: Replaced reserved exp identifier Vincent Lefevre
2025-07-02 14:41 ` Alejandro Colomar
2025-07-03 2:34 ` Vincent Lefevre [this message]
2025-07-03 2:58 ` Alejandro Colomar
2025-07-03 8:17 ` Vincent Lefevre
2025-07-03 16:28 ` Alejandro Colomar
2025-07-12 21:23 ` Vincent Lefevre
2025-07-19 13:42 ` Alejandro Colomar
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=20250703023451.GJ12583@qaa.vinc17.org \
--to=vincent@vinc17.net \
--cc=alx@kernel.org \
--cc=linux-man@vger.kernel.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox