Related articles |
---|
Stack frames & static predecessors wollenberg@web.de (Till Wollenberg) (2007-08-24) |
Re: Stack frames & static predecessors torbenm@app-3.diku.dk (2007-08-24) |
Re: Stack frames & static predecessors gah@ugcs.caltech.edu (glen herrmannsfeldt) (2007-08-24) |
Re: Stack frames & static predecessors tk@ic.unicamp.br (Tomasz Kowaltowski) (2007-08-24) |
Re: Stack frames & static predecessors bonzini@gnu.org (Paolo Bonzini) (2007-08-24) |
Re: Stack frames & static predecessors gene.ressler@gmail.com (Gene) (2007-08-24) |
Re: Stack frames & static predecessors anton@mips.complang.tuwien.ac.at (2007-08-25) |
Re: Stack frames & static predecessors dnovillo@acm.org (Diego Novillo) (2007-08-25) |
[3 later articles] |
From: | torbenm@app-3.diku.dk (Torben =?iso-8859-1?Q?=C6gidius?= Mogensen) |
Newsgroups: | comp.compilers |
Date: | Fri, 24 Aug 2007 08:56:57 +0200 |
Organization: | Department of Computer Science, University of Copenhagen |
References: | 07-08-065 |
Keywords: | Pascal, code |
Posted-Date: | 25 Aug 2007 10:34:11 EDT |
Till Wollenberg <wollenberg@web.de> writes:
> if some code of an inner function ('bar') accesses a local variable
> ('x') of an outer function ('foo') how is the address (on the stack)
> of this variable determined?
Look in chapter 9 (specifically section 9.7.3) of my book "Basics of
Compiler Design", which you can freely download from
http://www.diku.dk/~torbenm/Basics .
Torben
Return to the
comp.compilers page.
Search the
comp.compilers archives again.