[#9722] Kernel#system broken inside Dir.chdir(&block) if system command doesn't have shell characters — <noreply@...>

Bugs item #7278, was opened at 2006-12-14 13:59

8 messages 2006/12/14

[#9749] System V IPC in standard library? — Steven Jenkins <steven.jenkins@...>

Back in August, I needed a semaphore to serialize access to an external

14 messages 2006/12/19

[#9753] CVS freeze — SASADA Koichi <ko1@...>

Hi,

20 messages 2006/12/20
[#9755] Re: [ruby-dev:30039] CVS freeze — SASADA Koichi <ko1@...> 2006/12/20

Hi,

[#9757] Re: [ruby-dev:30040] Re: CVS freeze — SASADA Koichi <ko1@...> 2006/12/20

Hi,

Re: What's up with dates?

From: Eric Hodel <drbrain@...7.net>
Date: 2006-12-02 05:04:13 UTC
List: ruby-core #9659
On Dec 1, 2006, at 20:32 , Micah Wylde wrote:

> I have a question about why dates are like they are in ruby. In ruby,
> we have Date, DateTime, and Time, all of which seem to store about the
> same thing, but have vastly different methods with which to interact
> with the data, so the class you'd want to use varies according to what
> your task is. However, there isn't an easy way to convert between the
> three, which has caused a great deal of annoyance over the years I've
> been using Ruby.

Time is a time_t wrapper, and is limited in range by your OS (as  
small as 1970 to 2038).

Date is a ruby class and stores a date of unlimited range.

DateTime is a ruby class and stores a date and time of unlimited range.

> In general, the situation with dates and times seems against the ideas
> of ruby, and I'm curious how and why they came about, and whether
> anything is going to be done about it in 1.9. Can anyone enlighten me?

I haven't heard any plans, but patches will certainly hurry something  
like this along.

-- 
Eric Hodel - drbrain@segment7.net - http://blog.segment7.net

I LIT YOUR GEM ON FIRE!


In This Thread

Prev Next