| Line 159... |
Line 159... |
| 159 |
particular how it is printed. This is usually desirable, but if you
|
159 |
particular how it is printed. This is usually desirable, but if you
|
| 160 |
want to specify an object in a particular time zone but to be printed
|
160 |
want to specify an object in a particular time zone but to be printed
|
| 161 |
in the current time zone you may want to remove the \code{"tzone"}
|
161 |
in the current time zone you may want to remove the \code{"tzone"}
|
| 162 |
attribute (e.g., by \code{c(x)}).
|
162 |
attribute (e.g., by \code{c(x)}).
|
| 163 |
|
163 |
|
| - |
|
164 |
% NB: Do *NOT* change the line structure before the two \Sexpr{}s below, unless
|
| - |
|
165 |
% -- you update the Rd2HTML() regression check in ../../../../tests/reg-tests-1d.R :
|
| 164 |
Unfortunately, the conversion is complicated by the operation of time
|
166 |
Unfortunately, the conversion is complicated by the operation of time
|
| 165 |
zones and leap seconds (according to this version of \R's data,
|
167 |
zones and leap seconds (according to this version of \R's data,
|
| 166 |
%% Keep these two \Sexpr{} in sync with Rd2HTML() regression check in
|
- |
|
| 167 |
%% ../../../../tests/reg-tests-1d.R :
|
- |
|
| 168 |
\Sexpr{length(.leap.seconds)} days have been 86401 seconds long so
|
168 |
\Sexpr{length(.leap.seconds)} days have been 86401 seconds long so
|
| 169 |
far, the last being on (actually, immediately before)
|
169 |
far, the last being on (actually, immediately before)
|
| 170 |
\Sexpr{format(as.Date(utils::tail(.leap.seconds, 1)))}: the times of the
|
170 |
\Sexpr{format(as.Date(utils::tail(.leap.seconds, 1)))}: the times of the
|
| 171 |
extra seconds are in the object \code{.leap.seconds}). The details of
|
171 |
extra seconds are in the object \code{.leap.seconds}). The details of
|
| 172 |
this are entrusted to the OS services where possible. It seems that
|
172 |
this are entrusted to the OS services where possible. It seems that
|
The R Project SVN
R