issue-3a61fd3e9857e08e1936e34a15417d390470a9ff.yaml

--- !ditz.rubyforge.org,2008-03-06/issue 
title: should duk_char_code_at() return 0 if target is not a string?
desc: ""
type: :task
component: duk
release: 
reporter: Sami Vaarala <sami.vaarala@iki.fi>
status: :unstarted
disposition: 
creation_time: 2014-04-11 10:34:03.945743 Z
references: []

id: 3a61fd3e9857e08e1936e34a15417d390470a9ff
log_events: 
- - 2014-04-11 10:34:04.126597 Z
  - Sami Vaarala <sami.vaarala@iki.fi>
  - created
  - ""
- - 2014-06-09 08:44:51.240095 Z
  - Sami Vaarala <sami.vaarala@iki.fi>
  - unassigned from release v0.11
  - ""
- - 2014-06-09 08:45:39.732153 Z
  - Sami Vaarala <sami.vaarala@iki.fi>
  - commented
  - |-
    If this were to be done, other string API calls should also be consistent
    with the change.  For example, substring operation currently also requires
    a string; with this change, it would return an empty string (or perhaps
    undefined) if the argument was not a string.