|VB/VBA: Creating list of variables and parsing statements email@example.com (Howard Kaikow) (2000-11-26)|
|Re: VB/VBA: Creating list of variables and parsing statements firstname.lastname@example.org (2000-11-30)|
|Re: VB/VBA: Creating list of variables and parsing statements email@example.com (Scott Nicol) (2000-12-01)|
|Re: VB/VBA: Creating list of variables and parsing statements firstname.lastname@example.org (2000-12-03)|
|Date:||3 Dec 2000 01:01:41 -0500|
|Organization:||AOL Bertelsmann Online GmbH & Co. KG http://www.germany.aol.com|
|Posted-Date:||03 Dec 2000 01:01:39 EST|
Scott Nicol <email@example.com> schreibt:
> Variables declared anywhere with a procedure are
> accessible anywhere within a procure, so you have to
> parse all variables first (or patch up later, but
> this can make things more difficult).
When variables are used before they are declared, then VB assumes a
variable of type Variant. When the following Dim statement indicates a
different type, this is flagged as an error.
>- reserved words that are reserved only in certain
> contexts (i.e. "access", "append" and "binary"
This situation is common to many languages :-(
You're right with all (other) topics, and now I'm happy that I never
tried to really parse VB code. During the development of my
decompilers it was sufficient to only parse for declarations :-)
Return to the
Search the comp.compilers archives again.