Date: Wed, 29 May 2013 21:58:16 +1000 From: Jason Birch <jbirch@jbirch.net> To: "freebsd-current@freebsd.org" <freebsd-current@freebsd.org>, "freebsd-questions@freebsd.org" <freebsd-questions@freebsd.org> Subject: Re: BSD sleep Message-ID: <CAA=KUhuHGa5S4_OPP6hfHikDOEyMLar1PCAHOBUEi9DLar3DqA@mail.gmail.com> In-Reply-To: <CAPJF9wnGg8gjLew4ER9%2Byw47bX_9xXuZAgkZxfMVjYS_6CktJA@mail.gmail.com> References: <20130528230140.A5B396F448@smtp.hushmail.com> <51A541B5.3010905@gmail.com> <1369801479.2670.YahooMailNeo@web190706.mail.sg3.yahoo.com> <CAPJF9wnGg8gjLew4ER9%2Byw47bX_9xXuZAgkZxfMVjYS_6CktJA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> Seriously, that explanation about different hours is not enough to prevent > at least useful option. > like > sleep -f 1h > (-f means force convert, without it you can see good explanation why sleep > for 1 hour will be not sleep for 1 hour, and etc, and not get sleep at > all.). > Do one thing, and do it well. What you have proposed involves: * an additional force flag * interpolation of what follows the force flag (does m mean minutes, or months?) * expectations around time, time zones, and what an hours is. That fails the litmus test on complexity for me personally - it seems like a lot of complexity for not much gain. > P.S. There is already non-portable feature in sleep - non-integer, and I'm > sure that no one thought about some financists from various countries, who > used to specify long numbers with separator, e.g. 3.600, and this means for > them one hour and not 3 point 6 seconds. > This isn't a good reason for adding another non-portable feature.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAA=KUhuHGa5S4_OPP6hfHikDOEyMLar1PCAHOBUEi9DLar3DqA>