|
47 | 47 | # |
48 | 48 | # == \Time Internal Representation |
49 | 49 | # |
50 | | -# Conceptually, Time class uses a Rational value to represent the number of |
51 | | -# nanoseconds from _Epoch_, 1970-01-01 00:00:00 UTC. |
| 50 | +# Conceptually, Time class uses a rational value to represent the number of |
| 51 | +# seconds from _Epoch_, 1970-01-01 00:00:00 UTC. |
52 | 52 | # There are no boundary or resolution limitations. |
53 | 53 | # The value can be obtained using Time#to_r. |
54 | 54 | # |
55 | 55 | # The Time class always uses the Gregorian calendar. |
56 | 56 | # I.e. the proleptic Gregorian calendar is used. |
57 | 57 | # Other calendars, such as Julian calendar, are not supported. |
58 | 58 | # |
59 | | -# The implementation uses a signed 63 bit integer or Integer (Bignum) to |
60 | | -# represent the Rational values if possible. |
61 | | -# (The signed 63 bit integers are used regardless of 32 and 64 bit environments.) |
| 59 | +# The implementation uses a signed 63 bit integer, Integer (Bignum) object or |
| 60 | +# Ratoinal object to represent a rational value. |
| 61 | +# (The signed 63 bit integer is used regardless of 32 and 64 bit environments.) |
| 62 | +# The value represents the number of nanoseconds from _Epoch_. |
62 | 63 | # The signed 63 bit integer can represent 1823-11-12 to 2116-02-20. |
63 | | -# When Integer or Rational is used (before 1823, after 2116, under |
| 64 | +# When Integer or Rational object is used (before 1823, after 2116, under |
64 | 65 | # nanosecond), Time works slower than when the signed 63 bit integer is used. |
65 | 66 | # |
66 | 67 | # Ruby uses the C function +localtime+ and +gmtime+ to map between the number |
|
0 commit comments