On Sat, 20-Mar-2010 at 06:54PM +0100, Peter Dalgaard wrote:
[...]
| It seems to be completely system-dependent. On Fedora 9, I see
|
|user system elapsed
| 2.890 0.314 3.374
|
| but on openSUSE 10.3 it is
|
|user system elapsed
| 3.924 6.992 10.917
|
| At any rate, I
Let me lay this to rest. For some reason the OP did not use a
vectorized call to strptime but 10 individual calls (as well as
making *false* claims about what strptime does and what is 'completely
unnecessary', and seemingly being igorant of system.time()).
I do not believe this is ever
Thanks for the two posts.
What if the timezone is set? Then the issue of system calls for the
timezone falls away, no?
system.time(for (i in 1:10) strptime(2010-03-10 17:00:00, %F
%H:%M:%S, tz=DST))
Output on Linux Box (64-bit R 2.10.1 running on Intel Xeon E5520 @
2.27GHz):
user
[I am herewith re-posting this message on R-devel, as it seems to be the
most appropriate mailing list for this issue.]
Dear List,
From what I understand, strptime() simply converts from one class
representation to another; i.e., from character to POSIXct/POSIXlt.
One strange feature
Alexander Peterhansl wrote:
[I am herewith re-posting this message on R-devel, as it seems to be the
most appropriate mailing list for this issue.]
Dear List,
From what I understand, strptime() simply converts from one class
representation to another; i.e., from character to
