Author: tene Date: 2010-02-23 22:05:30 +0100 (Tue, 23 Feb 2010) New Revision: 29810
Modified: docs/Perl6/Spec/S02-bits.pod Log: [S02] Small prose fixes. No functional changes. Modified: docs/Perl6/Spec/S02-bits.pod =================================================================== --- docs/Perl6/Spec/S02-bits.pod 2010-02-23 18:32:48 UTC (rev 29809) +++ docs/Perl6/Spec/S02-bits.pod 2010-02-23 21:05:30 UTC (rev 29810) @@ -1176,10 +1176,10 @@ fractions. Notionally they are real numbers which may be implemented in any C<Real> type of sufficient precision, preferably a C<Rat> or C<FatRat>. (Implementations that make fixed-point assumptions about -the available precision subsecond precision are discouraged; the user +the available subsecond precision are discouraged; the user interface must act like real numbers in any case.) Interfaces that take C<Duration> arguments, such as sleep(), may also take C<Real> -arguments, but C<Instant> arguments must be explicitly created either +arguments, but C<Instant> arguments must be explicitly created via any of various culturally aware time specification APIs. A small number of C<Instant> values that represent common epoch instant values are also available. @@ -1192,7 +1192,7 @@ which returns a new C<Instant>.) In order to facilitate the writing of culturally aware time modules, the C<Instant> type provides C<Instant> values corresponding to various commonly used epochs, such as the -1958 TAI epoch, the POSIX epoch, the Mac epoch, and perhaps the year +1958 TAI epoch, the POSIX epoch, the Mac epoch, and perhaps the year 2000 epoch as UTC thinks of it. There's no reason to exclude any useful epoch that is well characterized in atomic seconds. All normal times can be calculated from those epoch instants using
