[#56329] [ruby-trunk - Bug #8722][Assigned] Refinements remain active beyond the end of an evaled string — "charliesome (Charlie Somerville)" <charliesome@...>

9 messages 2013/08/02

[#56333] [CommonRuby - Feature #8723][Open] Array.any? predicate returns true for empty array. — "nurettin (Nurettin Onur TUGCU)" <onurtugcu@...>

12 messages 2013/08/02

[#56368] [ruby-trunk - Bug #8730][Open] "rescue Exception" rescues Timeout::ExitException — "takiuchi (Genki Takiuchi)" <genki@...21g.com>

15 messages 2013/08/04

[#56407] [ruby-trunk - misc #8741][Open] email notification on bugs.ruby-lang.org is broken — "rits (First Last)" <redmine@...>

18 messages 2013/08/05

[#56524] [ruby-trunk - Bug #8770][Open] [PATCH] process.c: avoid EINTR from Process.spawn — "normalperson (Eric Wong)" <normalperson@...>

19 messages 2013/08/10

[#56536] [ruby-trunk - Feature #8772][Open] Hash alias #| merge, and the case for Hash and Array polymorphism — "trans (Thomas Sawyer)" <redmine@...>

24 messages 2013/08/11

[#56544] [ruby-trunk - Bug #8774][Open] rb_file_dirname return wrong encoding string when dir is "." — jiayp@... (贾 延平) <jiayp@...>

10 messages 2013/08/11

[#56569] [ruby-trunk - Feature #8781][Open] Use require_relative() instead of require() if possible — "ko1 (Koichi Sasada)" <redmine@...>

31 messages 2013/08/12
[#56582] [ruby-trunk - Feature #8781] Use require_relative() instead of require() if possible — "drbrain (Eric Hodel)" <drbrain@...7.net> 2013/08/12

[#56584] Re: [ruby-trunk - Feature #8781] Use require_relative() instead of require() if possible — SASADA Koichi <ko1@...> 2013/08/12

(2013/08/13 2:25), drbrain (Eric Hodel) wrote:

[#56636] Re: [ruby-trunk - Feature #8781] Use require_relative() instead of require() if possible — Aaron Patterson <tenderlove@...> 2013/08/16

On Tue, Aug 13, 2013 at 07:38:01AM +0900, SASADA Koichi wrote:

[#56634] [ruby-trunk - Feature #8788][Open] use eventfd on newer Linux instead of pipe for timer thread — "normalperson (Eric Wong)" <normalperson@...>

11 messages 2013/08/16

[#56648] [ruby-trunk - Bug #8795][Open] "Null byte in string error" on Marshal.load — "mml (McClain Looney)" <m@...>

17 messages 2013/08/16

[#56824] [ruby-trunk - Feature #8823][Open] Run trap handler in an independent thread called "Signal thread" — "ko1 (Koichi Sasada)" <redmine@...>

14 messages 2013/08/27

[#56878] [ruby-trunk - misc #8835][Open] Introducing a semantic versioning scheme and branching policy — "knu (Akinori MUSHA)" <knu@...>

11 messages 2013/08/30

[#56890] [ruby-trunk - Feature #8839][Open] Class and module should return the class or module that was opened — "headius (Charles Nutter)" <headius@...>

26 messages 2013/08/30

[#56894] [ruby-trunk - Feature #8840][Open] Yielder#state — "marcandre (Marc-Andre Lafortune)" <ruby-core@...>

14 messages 2013/08/30

[ruby-core:56787] Re: [ruby-trunk - Feature #8809][Open] Process.clock_getres

From: David MacMahon <davidm@...>
Date: 2013-08-22 23:01:16 UTC
List: ruby-core #56787
On Aug 22, 2013, at 3:37 PM, Tanaka Akira wrote:

> Process.clock_getres can return rational if it supports
> :rational_second as a unit.
>=20
> The current default of unit is :float_second and
> I think float is good enough.

Agreed.  Plus, if someone really wants, they can request nanosecond =
precision, which is all that clock_getres supports (at least on Linux).

>=20
>>> Process.clock_getres(:SUS_GETRUSAGE_BASED_CLOCK_PROCESS_CPUTIME_ID, =
:hertz) #=3D> 1000000.0
>>=20
>> How would you feel about supporting :ns and :hz as equivalents for =
:nanosecond and :hertz?
>=20
> It is difficult to support :microsecond in that style
> because the SI prefix, Greek m, is not representable in ASCII.

I know it's not SI, but I often use ASCII "u" for Greek m ("=B5"), so =
:microsecond would be aliased by :us.

> Someone may argue :hz should be :Hz.

No doubt! :-)

> I feel :float_s is bit curious.

How about separating the type and the resolution into two different =
parameters?

    Process.clock_getres(Process::CLOCK_MONOTONIC, :float, :second)

...or...

    Process.clock_getres(Process::CLOCK_MONOTONIC, Float, :second)

> So it is difficult to adopt :ns style as canonical style of unit.
>=20
> I think several aliases are possible but
> I'd like to concentrate to main feature.
> The discussion for what aliases should be added or not can be diverge.

Agreed.  I think the main feature is great!

>=20
>>> Note that
>>> Process.clock_getres(:POSIX_TIMES_BASED_CLOCK_PROCESS_CPUTIME_ID, =
:hertz) is the clock ticks per second (CLK_TCK) and
>>> Process.clock_getres(:ISO_C_CLOCK_BASED_CLOCK_PROCESS_CPUTIME_ID, =
:hertz) is CLOCK_PER_SEC.
>>> I wanted to access them easily to investigate emulated clock =
behaviors on
>>> various OSes.
>>=20
>> Those are some long symbols!  Are these intended only for =
experimental/investigative use?
>=20
> I choose the long symbols that is longer than =
Process::CLOCK_PROCESS_CPUTIME_ID.
> Basically users should use Process::CLOCK_PROCESS_CPUTIME_ID if no =
reason.

Sounds good.

Dave

In This Thread