issue-346c5bcfc17351640398bd6e2b39cddf2c8bbdfc.yaml

--- !ditz.rubyforge.org,2008-03-06/issue 
title: "API: remove duk_is_strict_call() from the public API"
desc: |-
  The duk_is_strict_call() now always returns 1 because in Duktape 0.12.0
  all Duktape API contexts are considered strict.  This is *not* the case
  for Duktape internally when an Ecmascript function is running, so the
  duk_is_strict_call() is still necessary -- it could just be removed from
  the public API.
type: :task
component: duk
release: v1.0
reporter: Sami Vaarala <sami.vaarala@iki.fi>
status: :closed
disposition: :fixed
creation_time: 2014-08-18 21:34:35.956938 Z
references: []

id: 346c5bcfc17351640398bd6e2b39cddf2c8bbdfc
log_events: 
- - 2014-08-18 21:34:36.138392 Z
  - Sami Vaarala <sami.vaarala@iki.fi>
  - created
  - ""
- - 2014-10-07 21:38:48.017737 Z
  - Sami Vaarala <sami.vaarala@iki.fi>
  - closed with disposition fixed
  - |-
    Keep the function, it might be possible to have lenient user functions at some
    point, and debugger functionality may need it.