Smalltalk › Pharo › Pharo Smalltalk Developers

Date&Time api

_‹ Previous Topic Next Topic _›

Classic

List

Threaded

3 messages Options

Uko2

Date&Time api

Hi,

there are some weird things around the data & time API. So time-related classes are using methods like #asNanoSeconds. And numbers do not implements it. But they do implement methods as #nanoSeconds, #milliSeconds, #seconds and #asSeconds. Of course "5 nanoSeconds” are nicer than “5 asNanoSeconds”. Maybe we can do something to maintain polymorphism?

Uko

Sean P. DeNigris

Re: Date&Time api

Administrator

Uko2 wrote

"5 nanoSeconds” are nicer than “5 asNanoSeconds”

And "5 nanoseconds" would be even nicer ;) http://forum.world.st/milliseconds-versus-milliSeconds-tt4809142.html

Cheers,
Sean

cbc

Re: Date&Time api

In reply to this post by Uko2

To, #asNanoSeconds converts the time into the umber of nanosecond that the time represents.

#nanoSeconds (and the others) create a duration that is to be added to the time or DateAndTime. The two do not end with the same things 0 and shouldin't.

The first tells you how many they represent; the second builds duration.

Probably not ideal names - but the intents are definitely different.

-cbc

On Tue, Aug 18, 2015 at 1:21 AM, Yuriy Tymchuk <[hidden email]> wrote:

Hi,

there are some weird things around the data & time API. So time-related classes are using methods like #asNanoSeconds. And numbers do not implements it. But they do implement methods as #nanoSeconds, #milliSeconds, #seconds and #asSeconds. Of course "5 nanoSeconds” are nicer than “5 asNanoSeconds”. Maybe we can do something to maintain polymorphism?

Uko