> Mick Jordan
> on Tue, 15 Mar 2016 19:50:48 -0700 writes:
> On 3/15/16 3:52 AM, Martin Maechler wrote:
>>> peter dalgaard
>>> on Sat, 12 Mar 2016 19:11:40 +0100 writes:
>> > OK, .Internal is not necessary to reproduce oddity in this area. I
also see things l
On 3/15/16 3:52 AM, Martin Maechler wrote:
peter dalgaard
on Sat, 12 Mar 2016 19:11:40 +0100 writes:
> OK, .Internal is not necessary to reproduce oddity in this area. I also
see things like (notice 1980)
>> strptime(paste0(sample(1900:1999,80,replace=TRUE),"/01/01"), "%Y/%m/%d"
> On 15 Mar 2016, at 11:52 , Martin Maechler wrote:
>
>
> o R version 3.3.0 (Supposedly Educational) prerelease versions will appear
> starting Monday 2016-03-14. Final release is scheduled for Thursday
> 2016-04-14.
Oops, that's actually incorrect. It's R-3.2.4-patched for a couple more da
Hi!
Some context for the tests Mick mentioned:
Our tests, which are part of the open-source FastR repository, consist of small
executable R snippets.
While working on FastR, we test regularly by comparing the output generated
when running them on FastR and GNUR.
Every difference hints at a probl
> peter dalgaard
> on Sat, 12 Mar 2016 19:11:40 +0100 writes:
> OK, .Internal is not necessary to reproduce oddity in this area. I also
see things like (notice 1980)
>> strptime(paste0(sample(1900:1999,80,replace=TRUE),"/01/01"), "%Y/%m/%d",
tz="CET")
...
OK, .Internal is not necessary to reproduce oddity in this area. I also see
things like (notice 1980)
> strptime(paste0(sample(1900:1999,80,replace=TRUE),"/01/01"), "%Y/%m/%d",
> tz="CET")
[1] "1942-01-01 CEST" "1902-01-01 CET" "1956-01-01 CET" "1972-01-01 CET"
[5] "1962-01-01 CET" "1900-0
On 3/12/16 12:33 AM, peter dalgaard wrote:
On 12 Mar 2016, at 00:05 , Mick Jordan wrote:
This is definitely obscure but we had a unit test that called .Internal(strptime,
"1942/01/01", %Y/%m/%d") with timezone (TZ) set to CET.
Umm, that doesn't even parse. And fixing the typo, it doesn't run:
> On 12 Mar 2016, at 00:05 , Mick Jordan wrote:
>
> This is definitely obscure but we had a unit test that called
> .Internal(strptime, "1942/01/01", %Y/%m/%d") with timezone (TZ) set to CET.
Umm, that doesn't even parse. And fixing the typo, it doesn't run:
> .Internal(strptime, "1942/01/01"
This is definitely obscure but we had a unit test that called
.Internal(strptime, "1942/01/01", %Y/%m/%d") with timezone (TZ) set to
CET. In R-3.1.3 that returned "1942-01-01 CEST" which, paradoxically, is
correct as they evidently did strange things in Germany during the war
period. Java also
