From: Wilson Bilkovich <wilsonb@...>
Date: 2005-12-19T06:45:57+09:00
Subject: Re: Time.utc! and Time.localtime!

> Hi,
>
> In message "Re: Time.utc! and Time.localtime!"
>     on Fri, 16 Dec 2005 00:56:21 +0900, ara.t.howard@noaa.gov writes:
>
> |   class Time
> |     alias_method "__utc__", "utc"
> |     alias_method "utc!", "__utc__"
> |     def utc *a, &b
> |       warn "#utc method will change - use #utc! for self modifying behaviour!"
> |       __utc__ *a, &b
> |     end
> |   end
> |
> |an some time might be enough to make the transition.
>
> I don't think this is good for transition, just because new code would
> still get complained.
>

What about #to_utc for the non-destructive version, and possibly a
warning on #utc if that is going to change in the future?

--Wilson.

(P.S. I had to use the mget command to get this message into my mail
system, so hopefully I haven't broken the threads for anyone.)