Dear all,
suppose I would have an abstract class in C++ representing some
complex type. Is it possible to expose a selected C++ interface
to R while retaining all the gory details within C++. Other
scripting languages have the concept of an opaque pointer and
constructor/destructor hooks, so
Dear all,
I have found the following (for me) incomprehensible behaviour of
ISOdate (POSIXct):
ISOdate(1900,6,16)
[1] 1900-06-15 14:00:00 Westeuropäische Sommerzeit
ISOdate(1950,6,16)
[1] 1950-06-16 14:00:00 Westeuropäische Sommerzeit
Note that in the first case I get the 15th of June back,
:
ISOdate(1900,6,16,tz=)
ISOdate(1950,6,16,tz=)
If you don't need timezones and don't want to worry about them
you can alternately use the chron library for your dates and
times.
---
Date: Wed, 19 Nov 2003 14:58:24 +0100
From: Heiko Schaefer [EMAIL PROTECTED]
To: [EMAIL PROTECTED
.
---
Date: Wed, 19 Nov 2003 14:58:24 +0100
From: Heiko Schaefer [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: [R] ISOdate returns incorrect date?
Dear all,
I have found the following (for me) incomprehensible behaviour of
ISOdate (POSIXct):
ISOdate(1900,6,16)
[1] 1900-06-15 14:00
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Re: [R] ISOdate returns incorrect date?
Heiko Schaefer [EMAIL PROTECTED] writes:
Does this really work for you? I still get:
ISOdate(1900,6,16)
[1] 1900-06-15 14:00:00 Westeuropäische Sommerzeit
ISOdate(1900,6,16,tz=)
[1] 1900-06-15 12
