From: dnovillo@acm.org   
      
   On 8/24/07, Gene  wrote:   
      
   > For this purpose, each scope contains a pointer called a   
   > "static link" (vice the dynamic link, which always points to the next   
   > lexically enclosing scope, regardless of its lexical nesting).   
      
   This is roughly the strategy used by GCC.  Once the program is   
   converted into GIMPLE (GCC's high-level IL), the nesting of functions   
   is decomposed using the static chain idea.  See the file   
   /gcc/tree-nested.c in a post 4.0 release of GCC.   
   (http://gcc.gnu.org/viewcvs/trunk/gcc/tree-nested.c?view=markup)   
      
   Also, you can ask GCC to dump the unnesting changes with -fdump-tree-nested.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)