issue-2110f01ab55e6ba5a867cbbd9e0582b5e3cc399f.yaml

--- !ditz.rubyforge.org,2008-03-06/issue 
title: remove eval() limitation requiring that a caller activation exists
desc: |-
  This normally has little effect, but if eval() is called from C code with an empty
  value stack, a TypeError is now thrown.
  
  This was seen in practice e.g. with the eventloop example where eval.bind()
  was used to create a callback function which was then called from C code.
type: :task
component: duk
release: v0.10
reporter: sva <sami.vaarala@iki.fi>
status: :closed
disposition: :fixed
creation_time: 2014-03-06 21:15:59.287423 Z
references: []

id: 2110f01ab55e6ba5a867cbbd9e0582b5e3cc399f
log_events: 
- - 2014-03-06 21:15:59.431605 Z
  - sva <sami.vaarala@iki.fi>
  - created
  - ""
- - 2014-03-08 01:47:46.595628 Z
  - sva <sami.vaarala@iki.fi>
  - closed with disposition fixed
  - ""