issue-7a8264bd5b25f9b5618a0e4e88644b7683b30c8b.yaml

--- !ditz.rubyforge.org,2008-03-06/issue 
title: "api: clean up duk_{put,get,del,has}_var() API calls"
desc: |-
  These API calls are not yet in use.  They'll become more relevant with
  introspection (required by e.g. debugging), in which case the API calls
  may be introspecting either Ecmascript or Duktape/C activations.
  
  A few notes from earlier API design:
  
  - duk_put_var(): There could be a return value indicating whether the put failed
    This is not relevant in strict mode, but in non-strict mode a variable put can
    silently fail.
  
  - duk_get_var(): Although Ecmascript semantics always require a ReferenceError for
    unresolvable identifiers, it might fit the API better to return zero if
    identifier is not found and non-zero if found.  This would match the property
    access API.
type: :task
component: duk
release: v1.1
reporter: Sami Vaarala <sami.vaarala@iki.fi>
status: :unstarted
disposition: 
creation_time: 2014-09-16 20:19:56.985664 Z
references: []

id: 7a8264bd5b25f9b5618a0e4e88644b7683b30c8b
log_events: 
- - 2014-09-16 20:19:57.182524 Z
  - Sami Vaarala <sami.vaarala@iki.fi>
  - created
  - ""