issue-52e53e2cd14fdb7052499f4e98746441735ed192.yaml

--- !ditz.rubyforge.org,2008-03-06/issue 
title: fix behavior of duk_push_string() and duk_push_lstring() for NULL arg
desc: ""
type: :task
component: duk
release: v0.7
reporter: sva <sami.vaarala@iki.fi>
status: :closed
disposition: :fixed
creation_time: 2013-06-12 20:47:26.499779 Z
references: []

id: 52e53e2cd14fdb7052499f4e98746441735ed192
log_events: 
- - 2013-06-12 20:47:26.816693 Z
  - sva <sami.vaarala@iki.fi>
  - created
  - ""
- - 2013-08-27 20:39:43.458282 Z
  - sva <sami.vaarala@iki.fi>
  - assigned to release v0.7 from v0.6
  - ""
- - 2013-10-25 21:10:40.123469 Z
  - sva <sami.vaarala@iki.fi>
  - closed with disposition fixed
  - |-
    The current behavior is to push 'undefined' if duk_push_string() is given
    a NULL pointer.  This seems intuitive and in fact matches Lua's
    lua_pushstring() behavior.