On 7/15/06, Duncan Murdoch <[EMAIL PROTECTED]> wrote:
> On 7/15/2006 1:37 PM, Gabor Grothendieck wrote:
> > On 7/15/06, Duncan Murdoch <[EMAIL PROTECTED]> wrote:
> >> On 7/15/2006 1:01 PM, Gabor Grothendieck wrote:
> >>> On 7/14/06, Duncan Murdoch <[EMAIL PROTECTED]> wrote:
> On 7/14/2006 3:38
On 7/15/2006 1:37 PM, Gabor Grothendieck wrote:
> On 7/15/06, Duncan Murdoch <[EMAIL PROTECTED]> wrote:
>> On 7/15/2006 1:01 PM, Gabor Grothendieck wrote:
>>> On 7/14/06, Duncan Murdoch <[EMAIL PROTECTED]> wrote:
On 7/14/2006 3:38 PM, Sebastian Luque wrote:
> Hi,
>
> One of the big
On 7/15/06, Duncan Murdoch <[EMAIL PROTECTED]> wrote:
> On 7/15/2006 1:01 PM, Gabor Grothendieck wrote:
> > On 7/14/06, Duncan Murdoch <[EMAIL PROTECTED]> wrote:
> >> On 7/14/2006 3:38 PM, Sebastian Luque wrote:
> >>> Hi,
> >>>
> >>> One of the big decisions when writing code is how to handle dates
On 7/15/2006 1:01 PM, Gabor Grothendieck wrote:
> On 7/14/06, Duncan Murdoch <[EMAIL PROTECTED]> wrote:
>> On 7/14/2006 3:38 PM, Sebastian Luque wrote:
>>> Hi,
>>>
>>> One of the big decisions when writing code is how to handle dates and
>>> times. Gabor Grothendieck provided an excellent overview
On 7/14/06, Duncan Murdoch <[EMAIL PROTECTED]> wrote:
> On 7/14/2006 3:38 PM, Sebastian Luque wrote:
> > Hi,
> >
> > One of the big decisions when writing code is how to handle dates and
> > times. Gabor Grothendieck provided an excellent overview of the issue in
> > his R News 4/1 (2004) article,
On 7/14/2006 3:38 PM, Sebastian Luque wrote:
> Hi,
>
> One of the big decisions when writing code is how to handle dates and
> times. Gabor Grothendieck provided an excellent overview of the issue in
> his R News 4/1 (2004) article, and many users and developers are probably
> using it as a guide
[Sorry for my previous empty post]
Dirk Eddelbuettel <[EMAIL PROTECTED]> wrote:
> On 14 July 2006 at 14:38, Sebastian Luque wrote:
> | If Gabor's recommendations are to be followed, wouldn't it make sense
> | to include chron in base R? Given that flexibility for handling time
> Future historia
On 14 July 2006 at 16:32, Gabor Grothendieck wrote:
| On 7/14/06, Dirk Eddelbuettel <[EMAIL PROTECTED]> wrote:
| > Date and POSIXt have served me well over the last few years. They are
| > maintained and being extended [ 1 ]. Chron, to the best of my knowledge, is
| > dead code so I'd bet against
Dirk Eddelbuettel <[EMAIL PROTECTED]> wrote:
On 14 July 2006 at 14:38, Sebastian Luque wrote:
| If Gabor's recommendations are to be followed, wouldn't it make sense to
| include chron in base R? Given that flexibility for handling time
Future historians will provide a fuller account of the ext
On 7/14/06, Dirk Eddelbuettel <[EMAIL PROTECTED]> wrote:
>
> On 14 July 2006 at 14:38, Sebastian Luque wrote:
> | If Gabor's recommendations are to be followed, wouldn't it make sense to
> | include chron in base R? Given that flexibility for handling time
>
> Future historians will provide a full
On 14 July 2006 at 14:38, Sebastian Luque wrote:
| If Gabor's recommendations are to be followed, wouldn't it make sense to
| include chron in base R? Given that flexibility for handling time
Future historians will provide a fuller account of the extended debates, but
my reading of these discuss
Hi,
One of the big decisions when writing code is how to handle dates and
times. Gabor Grothendieck provided an excellent overview of the issue in
his R News 4/1 (2004) article, and many users and developers are probably
using it as a guide. The proposed guideline is to use the simplest class
re
12 matches
Mail list logo
