[squeak-dev] Status of date problem

Chris Muller asqueaker at gmail.com
Sat Mar 19 16:43:19 UTC 2016


> If you’re touching this, would you mind changing the implementation to this?
>
>         ^self now utcOffset: offsetDuration

Yes, I thought about that, until...

>
> And we should think about deprecating utcOffset: and renaming it to ... atOffset:?

... I thought that I did not want to add another sender of a message I
didn't much like (utcOffset:).

+1, I like that.  #atOffset: can be thought of as a "converting"
method, same magnitude, just converted to be using a different "lense"
onto that magnitude (the offset).

>
>> I actually think we should get rid of DateAndTime>>#offset:, or at
>> least make it a private (or initializing) method.
>
> +1
>
> (if we deprecate it, we need to adjust the message in nowWithOffset:)

nowAtOffset:.   :)    Whew, I'm glad we're cleaningup the API a bit,
so this would be a good time to re-do the categories too.  We don't
use categories to delineate "ansi" from "squeak" anywhere else, I
don't find it helpful at all.  I'd like to make them more
conventional.


More information about the Squeak-dev mailing list