From: Florian Weimer <fweimer@redhat.com>
To: Adhemerval Zanella <adhemerval.zanella@linaro.org>
Cc: libc-alpha@sourceware.org
Subject: Re: [PATCH 1/2] Reinstate ftime and move define it for POSIX.1-2001 or older
Date: Wed, 21 Oct 2020 13:05:54 +0200 [thread overview]
Message-ID: <87sga7x2i5.fsf@oldenburg2.str.redhat.com> (raw)
In-Reply-To: <e39db04c-4a51-b735-a41a-b99f82a6c5bf@linaro.org> (Adhemerval Zanella's message of "Wed, 21 Oct 2020 08:03:33 -0300")
* Adhemerval Zanella:
>>> +/* Fill in TIMEBUF with information about the current time. */
>>> +
>>> +extern int ftime (struct timeb *__timebuf)
>>> + __nonnull ((1)) __attribute_deprecated__;
>>
>> Please use __attribute_deprecated_msg__, pointing towards clock_gettime.
>>
>> Should these deprecations be disabled for older POSIX?
>
> I think we should enforce these interface are really deprecated, and
> clock_gettime is provided with _POSIX_C_SOURCE >= 199309L.
Fair enough, so __attribute_deprecated_msg__ doesn't have to be made
conditional.
Thanks,
Florian
--
Red Hat GmbH, https://de.redhat.com/ , Registered seat: Grasbrunn,
Commercial register: Amtsgericht Muenchen, HRB 153243,
Managing Directors: Charles Cachera, Brian Klemm, Laurie Krebs, Michael O'Neill
next prev parent reply other threads:[~2020-10-21 11:06 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-19 19:13 Adhemerval Zanella
2020-10-19 19:13 ` [PATCH 2/2] time: Add 64-bit time_t support for ftime Adhemerval Zanella
2020-10-20 8:18 ` Lukasz Majewski
2020-10-27 17:38 ` Joseph Myers
2020-10-27 17:44 ` Adhemerval Zanella
2020-10-20 8:14 ` [PATCH 1/2] Reinstate ftime and move define it for POSIX.1-2001 or older Lukasz Majewski
2020-10-20 20:33 ` Adhemerval Zanella
2020-10-20 18:04 ` Szabolcs Nagy
2020-10-20 18:20 ` Adhemerval Zanella
2020-10-21 5:17 ` Florian Weimer
2020-10-21 11:03 ` Adhemerval Zanella
2020-10-21 11:05 ` Florian Weimer [this message]
2020-10-21 12:35 ` [PATCH v2] " Adhemerval Zanella
2020-10-26 12:17 ` Adhemerval Zanella
2020-10-26 16:03 ` Szabolcs Nagy
2020-10-26 16:13 ` Adhemerval Zanella
2020-10-26 16:19 ` Florian Weimer
2020-10-26 16:23 ` Adhemerval Zanella
2020-10-26 16:29 ` Florian Weimer
2020-10-26 17:09 ` Adhemerval Zanella
2020-10-28 13:54 ` Florian Weimer
2020-10-28 14:12 ` Zack Weinberg
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=87sga7x2i5.fsf@oldenburg2.str.redhat.com \
--to=fweimer@redhat.com \
--cc=adhemerval.zanella@linaro.org \
--cc=libc-alpha@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).