Message276479
As a person who keeps a close eye on the Austin Group mailing lists (i.e., 'the POSIX working group'), my guess is that it's very unlikely that POSIX will ever add those *_s() extensions. Here's a discussion on Reddit that actually captures all of the arguments pretty well:
https://www.reddit.com/r/C_Programming/comments/3ivi77/eli5_why_does_glibc_still_not_support_the/
That said, any API will do. The localtime_r() function has the disadvantage that the return value is a bit odd: can it return any other tm structure than the one provided? localtime_s() is a bit weird in that its input argument is stored after the output argument. Both functions also unnecessarily pass the time_t by reference. Maybe we can just pick a prototype that's as Pythonesque as possible that also fixes these shortcomings. Any thoughts? |
|
Date |
User |
Action |
Args |
2016-09-14 19:21:42 | EdSchouten | set | recipients:
+ EdSchouten, lemburg, tim.peters, belopolsky, pitrou, vstinner, akira |
2016-09-14 19:21:42 | EdSchouten | set | messageid: <1473880902.29.0.158189348761.issue28148@psf.upfronthosting.co.za> |
2016-09-14 19:21:42 | EdSchouten | link | issue28148 messages |
2016-09-14 19:21:42 | EdSchouten | create | |
|