From: Collin Funk <collin.funk1@gmail.com>
To: Alejandro Colomar <alx@kernel.org>
Cc: linux-man@vger.kernel.org
Subject: Re: [PATCH 1/3] man/man2/gettimeofday.2: Declare gettimeofday with [[deprecated]].
Date: Thu, 19 Jun 2025 15:55:30 -0700 [thread overview]
Message-ID: <878qlnqr31.fsf@gmail.com> (raw)
In-Reply-To: <c5sve7xkoc6cjs62dgevxqr2snxbmyehomtqvyxeetbpu4uipg@34i47s3a5adb>
[-- Attachment #1: Type: text/plain, Size: 1342 bytes --]
Hi Alex,
Alejandro Colomar <alx@kernel.org> writes:
> No, I don't like that. The type on its own line is fine IMO, but in the
> same line as the attribute looks weird.
>
> To me, OK:
>
> [[attr]] int foo(void);
>
> [[attr]]
> int foo(void);
>
> [[attr]]
> int
> foo(void); // I use this style when writing function definitions
>
> To me, not OK:
>
> [[attr]] int
> foo(void);
Okay, good to know the conventions. Thanks.
> Thanks! It might be good to CC libc-alpha@ and linux-api@ in such a
> patch. Or maybe it's overkill.
I will avoid it. I don't expect the syscalls to be removed as many old
programs still use them. And they work fine in most programs where
nanosecond resolution does not matter.
Also, currently glibc does not mark them as
[[deprecated]]/__attribute__ ((__deprecated__)) and I hope that it stays
that way for the foreseeable future. Apple, for example, marks functions
that are fine and used safely with deprecated and it causes many
annoying warnings when building programs. Specifically, any file that
uses sprintf or vfork will cause a warning on MacOS.
Anyways, submitted a v2 for patch 1/3 [1]. The other patches don't
depend on it. Just other things I have noticed.
Collin
[1] https://lore.kernel.org/linux-man/2d37d5a9251af3c1d25cf8e73e3585a9955d5772.1750373011.git.collin.funk1@gmail.com/T/#u
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2025-06-19 22:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-19 4:22 [PATCH 1/3] man/man2/gettimeofday.2: Declare gettimeofday with [[deprecated]] Collin Funk
2025-06-19 4:22 ` [PATCH 2/3] man/man3/ftime.3: Declare ftime " Collin Funk
2025-06-23 0:45 ` Alejandro Colomar
2025-06-19 4:22 ` [PATCH 3/3] man/man3/ftime.3: Correct POSIX standards in HISTORY Collin Funk
2025-06-23 0:53 ` Alejandro Colomar
2025-06-23 2:48 ` Collin Funk
2025-06-19 11:12 ` [PATCH 1/3] man/man2/gettimeofday.2: Declare gettimeofday with [[deprecated]] Alejandro Colomar
2025-06-19 17:54 ` Collin Funk
2025-06-19 22:20 ` Alejandro Colomar
2025-06-19 22:55 ` Collin Funk [this message]
2025-06-19 22:43 ` [PATCH v2] man/man2/gettimeofday.2: Declare functions " Collin Funk
2025-06-23 0:42 ` Alejandro Colomar
2025-06-23 2:42 ` Collin Funk
2025-06-23 3:09 ` G. Branden Robinson
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=878qlnqr31.fsf@gmail.com \
--to=collin.funk1@gmail.com \
--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 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.