issue-bcf0777e6f008837645abb3811574d44edebda3d.yaml

--- !ditz.rubyforge.org,2008-03-06/issue 
title: make eval strictness independent of Duktape/C activation state
desc: |-
  Currently strictness depends on whether or not a Duktape/C call is active,
  which is confusing, especially because variable declaration behavior in
  eval() code depends on strictness.
type: :task
component: duk
release: v0.12
reporter: Sami Vaarala <sami.vaarala@iki.fi>
status: :closed
disposition: :fixed
creation_time: 2014-07-23 21:20:12.304231 Z
references: []

id: bcf0777e6f008837645abb3811574d44edebda3d
log_events: 
- - 2014-07-23 21:20:12.492160 Z
  - Sami Vaarala <sami.vaarala@iki.fi>
  - created
  - ""
- - 2014-07-23 21:20:17.081419 Z
  - Sami Vaarala <sami.vaarala@iki.fi>
  - closed with disposition fixed
  - ""