Date: Fri, 25 Jan 2019 12:30:23 +0300 From: Valery Ushakov <u...@stderr.spb.ru> Message-ID: <20190125093023.gc18...@pony.stderr.spb.ru>
| As someone who actually have to ecnoutner locales in daily life and | not just think about them sitting in an ivory tower I don't understand | why do we even have this argument. Locale-specific argument to sleep | is pure madness, period (no pun intended). I am not sure why you are suddenly complaining, it has been like this for > 21 years... It cannot have bothered your too much, in your boring old stone tower, as until this week, you don't seem to have complained about it. Why now? And as I said before, if this is to be changed, it needs to be via a discussion in front of a wider audience than reads source-changes-d and in particular messages with a subject that refers to one of the more boring commands that we have. kre ps: in the meantime, I have changes to sleep which avoid the horrible '.' test, that I was never happy with, don't alter sleep's locale (using strtod_l as Joerg suggested --- why is that not documented?) and deal mor sensibly with long sleeps (nanosleep(2) is just plain weird when asked to sleep for a long time - sometimes it returns an error, other times it simply returns(0) immediately ... try sleep 1e15 for example). Those are not yet committed. But probably will be. Most of it has nothing to do with any locale issues.