issue-1f04e283b06d50a65c5f7db22a6393e9e47f4438.yaml

--- !ditz.rubyforge.org,2008-03-06/issue 
title: clean up value stack reserve + extra handling
desc: |-
  Currently there are only internal constants for value stack reservation.
  The duktape.h header should expose at least the reserve that a user can
  expect to have upon function entry.
  
  Also, currently on entry to a Duktape/C function only DUK_VALSTACK_INTERNAL_EXTRA
  value stack reserve is automatically allocated.  If this constant is really
  for internal use only, there is actually no user reservation by default.
  This should be fixed by adding the user reserve to the value stack check
  at least when entering a Duktape/C function (this isn't necessary for
  Ecmascript functions).
type: :task
component: duk
release: v2.0
reporter: sva <sami.vaarala@iki.fi>
status: :unstarted
disposition: 
creation_time: 2013-08-23 23:17:56.338437 Z
references: []

id: 1f04e283b06d50a65c5f7db22a6393e9e47f4438
log_events: 
- - 2013-08-23 23:17:56.511375 Z
  - sva <sami.vaarala@iki.fi>
  - created
  - ""
- - 2013-09-29 10:05:52.835362 Z
  - sva <sami.vaarala@iki.fi>
  - assigned to release v0.8 from v0.7
  - ""
- - 2013-11-26 22:06:07.480790 Z
  - sva <sami.vaarala@iki.fi>
  - assigned to release v0.9 from v0.8
  - ""
- - 2014-01-29 18:27:08.342258 Z
  - sva <sami.vaarala@iki.fi>
  - assigned to release v0.10 from v0.9
  - ""
- - 2014-04-12 09:11:00.262841 Z
  - Sami Vaarala <sami.vaarala@iki.fi>
  - assigned to release v0.11 from v0.10
  - ""
- - 2014-07-10 12:43:15.333936 Z
  - Sami Vaarala <sami.vaarala@iki.fi>
  - assigned to release v0.12 from v0.11
  - ""
- - 2014-09-09 11:29:50.292326 Z
  - Sami Vaarala <sami.vaarala@iki.fi>
  - assigned to release v1.0 from v0.12
  - ""
- - 2014-10-13 11:52:35.076737 Z
  - Sami Vaarala <sami.vaarala@iki.fi>
  - assigned to release v1.1 from v1.0
  - ""
- - 2014-11-02 00:14:49.976768 Z
  - Sami Vaarala <sami.vaarala@iki.fi>
  - assigned to release v2.0 from v1.1
  - ""