From: Mathieu Bouchard <matju@...>
Date: 2001-02-26T01:20:37+09:00
Subject: [ruby-talk:11537] Re: Time without seconds (updated/fixed)

On Sun, 25 Feb 2001, Yukihiro Matsumoto wrote:
> Hi,
> In message "[ruby-talk:11426] Re: Time without seconds (updated/fixed)"
>     on 01/02/24, Kevin Smith <sent@qualitycode.com> writes:
> |I guess this is now an RCR:
> Mike, please.
> |Add a method: Time#set(seconds <,microseconds)
> |This method, which is much like Time.at, will 
> |alter an existing Time object.
> I think making Time immutable is a big change.
> We must discuss carefully before making decision.
> 							matz.

Mutable, you mean. It is immutable right now. I'm against. It's the kind
of thing where you choose one side or the other, and which one doesn't
matter so much as staying on the same side.

I must admit it took me a lot of time to accept String being mutable in
Ruby. But I certainly wouldn't like it if you'd change it to immutable
tomorrow. (This was just an example). The ground must be solid; this is
not version zero anymore.

matju