Re: Q: How to preserve symbol table info through multiple pass compilation?

> I originally preserved the symbol table by saving the contents for a
> specific scope at the appropriate places in the parse tree, but this
> is giving me problems when I want to insert something new into the
> symbol table after the initial pass through the parse tree. I am
> playing around with the idea of representing the symbol table as a
> tree of scopes, with nested scopes being children of the scope they
> are nested in. This, however, gives me a problem with constructs like
> the following:
>
>
> void foo () {
> ...
> }
>
> int x;
>
> void boo() {
> ...
> }
>
> 'x' should be visible to boo but not foo even though they have the
> same parent scope.


Your idea of using tree of scopes is just fine. The problem is with
"C". Each declaration in C introduces a new scope. In other words,
boo and foo do not share the same parent scope, there are at least 3
scopes illustrated in your fragment. The scope including the
declaration of foo, the scope nested inside that which also has an x
inside it, and the scope inside that that adds a boo.


-Chris Clark
--

Return to the comp.compilers page.
Search the comp.compilers archives again.