|Backpatch? firstname.lastname@example.org (Nikos Diamantopoulos) (1995-06-25)|
|Re: Backpatch? email@example.com (1995-06-30)|
|Re: Backpatch? firstname.lastname@example.org (1995-07-01)|
|Re: Backpatch? IanC@gibside.demon.co.uk (Ian Cull) (1995-07-05)|
|Re: Backpatch? email@example.com (1995-07-13)|
|Re: Backpatch? firstname.lastname@example.org (1995-07-19)|
|Re: Backpatch? email@example.com (1995-07-20)|
|Re: Backpatch? firstname.lastname@example.org (1995-07-20)|
|Organization:||University of Louisville|
|Date:||Sat, 1 Jul 1995 22:31:49 GMT|
|Received-Date:||Sat, 1 Jul 1995 18:35:17 -0400|
Nikos Diamantopoulos <email@example.com> writes:
> I need a backpatch mechanism such that i can use a variable before its
> definition. There are languages such as ALGOL, PL/1 that make use of
> such a mechanism.
> If anybody knows something about, he would greatly help me.
Why not use a simple linked list? That's what I do. Every
time you use an undefined variable link the code address and the variable
name into the lst. At the end of the compile traverse the list doing
symbol lookups and complain if anything is undefined.
Return to the
Search the comp.compilers archives again.