On 12/12/2012, at 18:37, Rick Waldron wrote:
>
> On Wed, Dec 12, 2012 at 2:17 AM, Isaac Schlueter <[email protected]> wrote:
> On Tue, Dec 11, 2012 at 7:18 PM, spqr <[email protected]> wrote:
> > maybe my question should have been "why does JavaScript have eval()?" ;-)
>
> I think a lot of people have wondered the same thing.
>
> Yes, it has its uses, but at this point, I don't know of any that
> aren't better served using some other mechanism. eval() has weird
> optimization-destroying semantics that cannot ever be changed, due to
> the fact that JavaScript must be backwards compatible forever.
>
>
> Runtime code generation? new Function( thecode ) works just as well, I guess
...sometimes:
(function (p) {
eval("(function(){console.log(p)})")();
try {
Function("console.log(p)")();
}
catch (e) {
console.log("FAIL -> "+ e.message);
}
})("OK");
OK
FAIL -> Can't find variable: p
--
Jorge.
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups "nodejs" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en
