Re: Standard library - date and time
- Posted by Jeremy Cowgar <jeremy at cowg?r?com> Apr 22, 2008
- 1084 views
I agree with a few points made. 1. Let's not change the existing date() and time() functions. We are adding to the standard library, not redesigning it. If there was a major flaw, that may be different, but date() currently provides information than many applications rely on and it will provide all the information that many people need. As time progresses, it may become used less and less and maybe at that time we can visit the idea of deprecating it (if that time comes). 2. We should prefix some things. For instance, the map functions deal with maps and task function deal with tasks. They are very specific and are not generic functions such as, min, max, remove, etc... I think date_now(), datetime_now() makes sense. For instance, we may be date_to_seconds() and also time_to_seconds(). We *need* to prefix those for them to make sense. to_seconds() ... how would it know if it's working on a date, time or both? I have found three email addresses for Carl (author of datetime) and have sent an email asking if it could be included in Euphoria. datetime has a copyright statement and no released license. -- Jeremy Cowgar http://jeremy.cowgar.com