Update on ES3.1 block scoped function declarations

Mark S. Miller erights at google.com
Thu Jul 10 15:28:48 PDT 2008

On Thu, Jul 10, 2008 at 2:51 PM, Allen Wirfs-Brock <
Allen.Wirfs-Brock at microsoft.com> wrote:

>  I see, yes there is a potential eval tax.  If I thought this was really a
> concern (and as you say, we already have the issue for catch and such) I'd
> be more inclined to fiddling with the scoping rule of eval rather than
> discarding lexically scoped consts.  BTW, I think many of the use cases for
> such const are more in support of code generators then actual end user
> programming.
Could you explain the "eval tax" issue you guys are concerned about? I don't
get it. Thanks.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.mozilla.org/pipermail/es-discuss/attachments/20080710/ef09095d/attachment-0002.html 

More information about the Es4-discuss mailing list