Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
| From | Keith Thompson <Keith.S.Thompson+u@gmail.com> |
|---|---|
| Newsgroups | comp.std.c |
| Subject | Re: Remove all standard library functions that depend on intmax_t |
| Date | 2020-05-07 16:54 -0700 |
| Organization | None to speak of |
| Message-ID | <87r1vvti6o.fsf@nosuchdomain.example.com> (permalink) |
| References | <r90pk2$kcn$1@solani.org> |
Philipp Klaus Krause <pkk@spth.de> writes:
> At the spring WG14 meeting, there were various proposals on how to deal
> with the intmax_t problem (intmax_t being baked into ABIs makes it hard
> to grow it). One would have been to remove all use of intmax_t in the
> standard libary to get it out of the ABI. But in the end, a much more
> radical decision was made: Remove intmax_t without replacement.
Do you have a reference to this? Did they really decide to remove
intmax_t altogether?
http://www.open-std.org/jtc1/sc22/wg14/www/docs/n2498.pdf (dated
2020-02-29) is a proposal to keep (u)intmax_t but deprecate library
functions that depend on them. Removing (u)intmax_t altogether would
break existing code.
See http://www.open-std.org/jtc1/sc22/wg14/www/docs/PreFreiburg2020.htm
for some other similar proposals.
[...]
--
Keith Thompson (The_Other_Keith) Keith.S.Thompson+u@gmail.com
Working, but not speaking, for Philips Healthcare
void Void(void) { Void(); } /* The recursive call of the void */
Back to comp.std.c | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Remove all standard library functions that depend on intmax_t Philipp Klaus Krause <pkk@spth.de> - 2020-05-07 12:58 +0200
Re: Remove all standard library functions that depend on intmax_t Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2020-05-07 16:54 -0700
Re: Remove all standard library functions that depend on intmax_t Philipp Klaus Krause <pkk@spth.de> - 2020-05-08 21:42 +0200
csiph-web