Open GoogleCodeExporter opened 9 years ago
Aaand I didn't read the section headers when filling them in, sorry. Still on
0.706
Original comment by megazzt
on 22 Jun 2011 at 3:08
Hi, this is a known issue due to eval having some magic properties with respect
to scope. I've written a bit more detailed blog post on the topic here:
http://radi.r-n-d.org/2011/02/evil-magic-of-eval.html
Original comment by rad...@gmail.com
on 22 Jun 2011 at 6:14
Ew yeah I get that; I actually noticed some of that myself when working with
eval() (I do not use it myself, but it seems some of my coworkers are fond of
it).
I think I even tried to override the context of eval once and realized I
couldn't do it.
What you guys need to do is write a JS engine in JS and then use it for eval().
;) Problem solved!
Original comment by megazzt
on 23 Jun 2011 at 7:13
Writing a new JS engine might be an overkill for this task. I'll mark it as
accepted for now, but don't guarantee quick resolution.
Original comment by r...@google.com
on 6 Jul 2011 at 2:29
Original issue reported on code.google.com by
megazzt
on 22 Jun 2011 at 3:07