Re: Standard library - date and time

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

c.k.lester wrote:
> 
> No, it's not broken (yet). I'm saying that we should co-opt date() and time()
> to do what they really should do: give the date and give the time. Yes, that
> will break code, but I think it benefits the language going forward.
>

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

Also, if so, if we are going to break things, wouldn't the "date" would be
better used as a type instead of a function? same with time and datetime ?

Before breaking anything though, I'd like to have more opinions.

--
Jeremy Cowgar
http://jeremy.cowgar.com

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

Search



Quick Links

User menu

Not signed in.

Misc Menu