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
On Wed, Oct 24, 2012 at 1:23 PM, Joe Rickerby <joe.rickerby@square-i.net> wrote:
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?
that looks indeed like a problem. Could you please check if you can implement the fix and then report it on google issue tracker? -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill
Joe Rickerby wrote:
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
Not really the answer your looking for, but my natural speak patterns are: "zero point five hours" "half anHour"
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 <joe.rickerby@square-i.net>
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
If it not use I don't know but the message 1 hour makes sense to me. cheers, Fabrizio 2012/10/24 Santiago Bragagnolo <santiagobragagnolo@gmail.com>
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 <joe.rickerby@square-i.net>
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
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 <fabrizio.perin@gmail.com> 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 <santiagobragagnolo@gmail.com>
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 <joe.rickerby@square-i.net>
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
2012/10/24 Camillo Bruni <camillobruni@gmail.com>
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!
well, you can actually write 2 hours ;P But I agree that the API should be improved
https://code.google.com/p/pharo/issues/detail?id=6876
On 2012-10-24, at 14:52, Fabrizio Perin <fabrizio.perin@gmail.com> 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 <santiagobragagnolo@gmail.com>
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 <joe.rickerby@square-i.net>
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
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 <camillobruni@gmail.com<mailto:camillobruni@gmail.com>> 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 <fabrizio.perin@gmail.com> 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 <santiagobragagnolo@gmail.com> 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 <joe.rickerby@square-i.net> 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.
A Second, I have prepared a howto add a fix video :) On 2012-10-24, at 16:14, Joe Rickerby <joe.rickerby@square-i.net> 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 <camillobruni@gmail.com<mailto:camillobruni@gmail.com>> 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 <fabrizio.perin@gmail.com> 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 <santiagobragagnolo@gmail.com>
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 <joe.rickerby@square-i.net>
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
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.
Yes, the singular forms should return the same as the plural ones, that is the only thing that makes sense. On 24 Oct 2012, at 16:14, Joe Rickerby <joe.rickerby@square-i.net> 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 <camillobruni@gmail.com> 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 <fabrizio.perin@gmail.com> 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 <santiagobragagnolo@gmail.com>
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 <joe.rickerby@square-i.net>
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
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.
-- Sven Van Caekenberghe http://stfx.eu Smalltalk is the Red Pill
Hi joe did you sign the license agreement? Stef On Oct 24, 2012, at 4:14 PM, Joe Rickerby 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 <camillobruni@gmail.com> 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 <fabrizio.perin@gmail.com> 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 <santiagobragagnolo@gmail.com>
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 <joe.rickerby@square-i.net>
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
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.
Nope, point me in the direction of it please. Couldn't find it on the wiki at http://code.google.com/p/pharo/wiki/LicenseAgreement Joe On 24 Oct 2012, at 6:55pm, Stéphane Ducasse <stephane.ducasse@inria.fr<mailto:stephane.ducasse@inria.fr>> wrote: Hi joe did you sign the license agreement? Stef On Oct 24, 2012, at 4:14 PM, Joe Rickerby 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 <camillobruni@gmail.com<mailto:camillobruni@gmail.com>> 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 <fabrizio.perin@gmail.com> 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 <santiagobragagnolo@gmail.com> 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 <joe.rickerby@square-i.net> 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.
On Oct 25, 2012, at 12:23 PM, Joe Rickerby <joe.rickerby@square-i.net> wrote:
Nope, point me in the direction of it please. Couldn't find it on the wiki at http://code.google.com/p/pharo/wiki/LicenseAgreement
Ups, that was lost in a cleanup.... we should restore the page. The documents are here: http://pharo.gforge.inria.fr/licenseDocuments/
Joe
On 24 Oct 2012, at 6:55pm, Stéphane Ducasse <stephane.ducasse@inria.fr> wrote:
Hi joe
did you sign the license agreement?
Stef
On Oct 24, 2012, at 4:14 PM, Joe Rickerby 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 <camillobruni@gmail.com> 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 <fabrizio.perin@gmail.com> 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 <santiagobragagnolo@gmail.com>
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 <joe.rickerby@square-i.net>
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
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.
-- Marcus Denker -- http://marcusdenker.de
I should add that there are a lot of similar methods with this behaviour on number, there's day, hour, milliSecond, minute, nanoSecond, second, week. If behaviour was changed, or it was simply deleted, it should probably be in all or none of the above to maintain consistency. On 24 Oct 2012, at 1:45pm, Santiago Bragagnolo <santiagobragagnolo@gmail.com<mailto:santiagobragagnolo@gmail.com>> wrote: 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 <joe.rickerby@square-i.net<mailto:joe.rickerby@square-i.net>> 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
participants (9)
-
Ben Coman -
Camillo Bruni -
Damien Cassou -
Fabrizio Perin -
Joe Rickerby -
Marcus Denker -
Santiago Bragagnolo -
Stéphane Ducasse -
Sven Van Caekenberghe