--- !ditz.rubyforge.org,2008-03-06/issue 
title: change default API strictness to 'strict' instead of 'non-strict'; would unify API usage in empty vs. nonempty stack case
desc: ""
type: :task
component: duk
release: v0.12
reporter: sva <sami.vaarala@iki.fi>
status: :closed
disposition: :fixed
creation_time: 2014-03-07 13:03:49.151025 Z
references: []

id: 9c6be1993e30ff5348bcf4ddde1177343f2d5a2c
log_events: 
- - 2014-03-07 13:03:49.306756 Z
  - sva <sami.vaarala@iki.fi>
  - created
  - ""
- - 2014-03-08 01:18:04.555165 Z
  - sva <sami.vaarala@iki.fi>
  - commented
  - |-
    Work branch is api-default-strictness.
    
    The trivial approach has the drawback that C code can no longer eval or compile
    anything non-strict.  This could be mitigated with additional flags, but this is
    less trivial than seems at first.
- - 2014-04-10 10:12:45.083940 Z
  - Sami Vaarala <sami.vaarala@iki.fi>
  - assigned to release v0.11 from v0.10
  - ""
- - 2014-07-10 12:43:19.643057 Z
  - Sami Vaarala <sami.vaarala@iki.fi>
  - assigned to release v0.12 from v0.11
  - ""
- - 2014-07-24 09:53:13.964754 Z
  - Sami Vaarala <sami.vaarala@iki.fi>
  - commented
  - Now that eval strictness handling was changed this should be more feasible again.
- - 2014-08-18 21:37:16.027445 Z
  - Sami Vaarala <sami.vaarala@iki.fi>
  - closed with disposition fixed
  - ""