Re: Standard library - date and time

new topic     » goto parent     » topic index » view thread      » older message » newer message

Jeremy Cowgar wrote:
> I think we need to decide. Do we want to have 3 types representing dates and
> times? date, time and datetime ?

I strongly vote for only one type: datetime.

Reasons:
- this is Euphoria (simple!) not perl or some other complicated languages
- why would someone use time type? It is just a bunch of seconds grouped in 60
and 60*60. No difficult math there.
- even Java only have Date (which is date + time), no Time or specific Date
- having date type does not speed calculation, only difference with datetime is
there is no need to multiply with 86400
- we don't need to break existing codes by using "date" and "time" for type
names or function names (important!)

new topic     » goto parent     » topic index » view thread      » older message » newer message

Search



Quick Links

User menu

Not signed in.

Misc Menu