--- !ditz.rubyforge.org,2008-03-06/issue 
title: implement first version of Date built-in
desc: |-
  The first version must be Ecmascript compliant, but does not need to be
  optimized yet.
  
  The E5/E5.1 is quite loose in specifying many aspects of Date behavior.
  For instance:
  
  * Date parsing must handle an ISO 8601 subset, but can also parse anything
    else; strict compliance does not require anything else, but real world
    compatibility might.
  
  * String-formatting is implementation defined (even for non-locale-specific
    formats).  Strict compliance does not require anything particular, but
    real world compatibility might.
  
  The "real world requirements" need separate investigation after the initial
  implementation is complete (separate issues should be opened).
  
  The initial implementation should rely on a minimal number of platform
  mechanisms (like locales).  These can serve as a baseline even if locale
  specific formatting is added later.
type: :task
component: duk
release: v0.2
reporter: sva <sami.vaarala@iki.fi>
status: :closed
disposition: :fixed
creation_time: 2013-02-17 01:35:25.503819 Z
references: []

id: 37af3b7f642f7b82a708866659b4536cfa8b439a
log_events: 
- - 2013-02-17 01:35:28.819163 Z
  - sva <sami.vaarala@iki.fi>
  - created
  - ""
- - 2013-02-17 01:43:16.356199 Z
  - sva <sami.vaarala@iki.fi>
  - assigned to release v0.2 from unassigned
  - ""
- - 2013-02-20 23:29:32.455250 Z
  - sva <sami.vaarala@iki.fi>
  - closed with disposition fixed
  - ""