Message-ID: <B4FC2AD1-48ED-4942-B9E7-807CACADA5A3@comcast.net>
Date: 2009-02-10T16:51:29Z
From: David Winsemius
Subject: Strange behaviour of ISOdatetime
In-Reply-To: <20090210152751.4FFC19870F@smtp2.ualg.pt>
My guess is that your two machines have different setting for locale.
What does this produce on each of them:
sessionInfo()$locale
(Note: It would have been part of the information that you were asked
to provide per the posting guide.)
---
For questions about unexpected behavior or a possible bug, you should,
at a minimum, copy and paste the output from sessionInfo() into your
message. When mentioning version numbers, always use the full version
number, e.g., `2.6.1', not just `2.6', and also mention the platform
(Windows, Linux, MacOS X, with their versions). Other potentially
relevant details include the locale (type Sys.getlocale() at the R
prompt), and whether you installed a pre-compiled binary version of R
or compiled it yourself.
--
David Winsemius
On Feb 10, 2009, at 11:31 AM, Pedro de Barros wrote:
> Hi All,
>
> I am watching a strange behaviour of ISOdatetime. In my work
> computer, I get NA when I try to do
> > ISOdatetime(1995,03,26,2,0,0)
> [1] NA
>
> But on other dates and/or times (hour) works OK
> > ISOdatetime(1995,03,25,2,0,0)
> [1] "1995-03-25 02:00:00 GMT"
>
> In my home computer, I do not have this problem.
> I am running the same version of R (2.8.1 patched) on both machines,
> the same version of Gnu Emacs (22.3.1) and the same version of ESS
> (5.3.10). Both are running Windows XP. Has anyone experienced this
> before?
>
> Pedro
>
> ______________________________________________
> R-help at r-project.org mailing list
> https://stat.ethz.ch/mailman/listinfo/r-help
> PLEASE do read the posting guide http://www.R-project.org/posting-guide.html
> and provide commented, minimal, self-contained, reproducible code.