[Date Prev][Date Next][Thread Prev][Thread Next]
[Date Index]
[Thread Index]
- Subject: Re: The removal of function environments: An opportunity for optimization?
- From: Roberto Ierusalimschy <roberto@...>
- Date: Tue, 25 May 2010 17:12:51 -0300
> > >What gets the surrounding _ENV declaration are *chunks*, not functions.
> > >Everything inside the same chunk (a compilation unit) share the same
> > >_ENV, unless there are explicit declarations of other _ENVs.
> > Sure. However, the "body" of a function is a chunk isn't it?
>
> No. A chunk is a compilation unit, that is, a string or file (or
> whatever) being loaded together. (The manual says that "syntactically, a
> block is the same as a chunk", but the "syntactically" may get lost when
> reading the BNF.)
(We will correct the manual to make things clearer. The correct
description should be that a chunk is a block, not that a block is a
chunk...)
-- Roberto
- References:
- The removal of function environments: An opportunity for optimization?, Mark Hamburg
- Re: The removal of function environments: An opportunity for optimization?, Edgar Toernig
- Re: The removal of function environments: An opportunity for optimization?, Roberto Ierusalimschy
- Re: The removal of function environments: An opportunity for optimization?, Mark Hamburg
- Re: The removal of function environments: An opportunity for optimization?, GrayFace
- Re: The removal of function environments: An opportunity for optimization?, Roberto Ierusalimschy
- Re: The removal of function environments: An opportunity for optimization?, Tomas Guisasola Gorham
- Re: The removal of function environments: An opportunity for optimization?, Roberto Ierusalimschy
- Re: The removal of function environments: An opportunity for optimization?, Tomas Guisasola Gorham
- Re: The removal of function environments: An opportunity for optimization?, Roberto Ierusalimschy