A Second, I have prepared a howto add a fix video :)

On 2012-10-24, at 16:14, Joe Rickerby <[email protected]> wrote:

> I'd be very happy if hour just returned the same as hours. I can also make 
> the change, but I've never done one before, do I submit it to Pharo inbox?
> 
> On 24 Oct 2012, at 2:28pm, Camillo Bruni 
> <[email protected]<mailto:[email protected]>> wrote:
> 
> the current implementation does not make any sense.
> despite the grammatical correctness of (1 hour) and the implied
> mistake of (2 hour). I think we should change or remove it!
> 
> https://code.google.com/p/pharo/issues/detail?id=6876
> 
> 
> 
> On 2012-10-24, at 14:52, Fabrizio Perin <[email protected]> wrote:
> If it not use I don't know but the message
> 1 hour
> 
> yes, but technically 0.5 hour is correct (though silly it does not work
> properly..)
> 
> makes sense to me.
> 
> cheers,
> Fabrizio
> 
> 2012/10/24 Santiago Bragagnolo <[email protected]>
> 
> I found almost no senders of #Number>>hour, and also have not sense at
> all. Probably we want to remove it.
> 
> 
> 2012/10/24 Joe Rickerby <[email protected]>
> 
> I can't believe I'd be the first person to find this, so sorry if this
> has been discussed before.
> 
> I was writing some code today, using Durations. I've come across the
> hour/hours methods before, and so I know that '2 hour' is really one hour,
> and that you have to write '2 hours' to have the thing work as expected.
> 
> It's a little strict for the language to do this, but I can see the logic.
> 
> What doesn't work for me is when I write '0.5 hour' or '(1/2) hour'. Both
> will return a duration of 1 hour. In my head I pronounce this 'half an
> hour', so it's an entirely reasonable thing to write.
> 
> Can something be done about this?
> 
> Joe
> 
> 
> 
> 
> Joe Rickerby
> Software Developer
> 
> Square [i] International
> 41 Maltby Street
> London
> 
> http://www.square-i.net
> 
> P Please consider the environment before printing this email
> 
> This e-mail message (including its attachments) is private, is intended for 
> the recipient named in it and may contain material which is confidential and 
> privileged. No-one other than the named recipient may read, copy, rely on, 
> redirect, save or alter the message or any part of it or any attachment to it 
> in any way. Square Group does not accept legal responsibility for the 
> contents of this message. Any views or opinions presented are solely those of 
> the author and do not represent those of Square Group Ltd unless otherwise 
> specifically stated. While reasonable effort has been made to ensure this 
> message is free of viruses, opening and using this message is at the risk of 
> the recipient.


Reply via email to