Path: csiph.com!news.mixmin.net!eternal-september.org!reader01.eternal-september.org!.POSTED!not-for-mail From: Tim Rentsch Newsgroups: comp.std.c Subject: Re: C23: asctime is obsolescent Date: Mon, 02 Jan 2023 08:11:44 -0800 Organization: A noiseless patient Spider Lines: 22 Message-ID: <861qocrk5b.fsf@linuxsc.com> References: <875yf5ksn9.fsf@nosuchdomain.example.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Injection-Info: reader01.eternal-september.org; posting-host="60a7a09099a9247382aee0cc66dfd4bb"; logging-data="1933247"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX19qNLSVO3O6FnSDyi47ulvLkS9w6r/kymo=" User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.4 (gnu/linux) Cancel-Lock: sha1:xH7YjSdtkY5GsO3k9O+meAUk+Lo= sha1:u7B6/K3Yf54Md6yBDWCxra0eABo= Xref: csiph.com comp.std.c:6461 Keith Thompson writes: > In the latest C23 draft: > https://www.open-std.org/jtc1/sc22/wg14/www/docs/n3047.pdf > the descriptions of the __DATE__ and __TIME__ macros refer to the > asctime() function. > > That's not new. What's new is that asctime() is deprecated. > > Referring to a deprecated function isn't really a problem, but if > asctime() is actually removed in a future standard the descriptions of > __DATE__ and __TIME__ will need to be updated. > > It would also be nice to have a new macro that expands to the current > date in the form "YYYY-MM-DD". I do not suggest changing the behavior > of __DATE__, but perhaps something like __ISODATE__ could be added. > Question: If this is done, should __DATE__ be deprecated? It seems pointless to add __ISODATE__ if __DATE__ is retained, and worse than pointless to add __ISODATE__ and then remove __DATE__. Similar comments apply to __TIME__, which also refers to asctime().