Ok, so I read Chrisâ e-mail and Iâm intrigued. Sven, youâre still right about financial months being 30 days for instance but the thing is that the current implementation seems broken (or inconsisten at least) and doesnât honor that case either. *Not* making the change will not help us either⦠So Iâd say: letâs do it. If somebody objects (or proposes a change) then we can handle that but at least we can claim that we try to give the users what we preach, like writing natural language like code (e.g. âx + 1 monthâ which is currently not possible). Thatâs my view at least. Also: weâre changing so much stuff in Pharo anyway all the time, I donât think this would hurt. Cheers, Max On 19.09.2014, at 14:37, Max Leske <maxleske@gmail.com> wrote:
Oops. Didnât realize that thread was from Squeak dev. So thereâs no Pharo implementation of that change for now anyway.
On 19.09.2014, at 14:35, Max Leske <maxleske@gmail.com> wrote:
On 19.09.2014, at 14:16, Sean P. DeNigris <sean@clipperadams.com> wrote:
Max Leske wrote
your change
It's not mine. I just scanned the thread from Squeak Dev and was intrigued because I've run into this limitation (the tension between year/month/etc as a conceptual ideal, and those entities as a specific number of days in context) a bunch before
Ok. Then Iâll look at it.
----- Cheers, Sean -- View this message in context: http://forum.world.st/Interesting-Date-Time-Thread-on-Squeak-Dev-tp4778652p4... Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.