Reverse engineering VB to document

[LarrySkelly]

I need to reverse-engineer some VB code to produce system documentation, and of course to support forward-engineering of the code.

Two questions:

1.  Other than what is in the user guide, is there a recommended approach?

2.  How does EA parse out VB comments - what are the rules?  it appears that it picks up comment lines prefixed with '' (two single quotes) that appear in front of procedeure declarations.  Are the full rules documented anywhere? (I've looked).

3.  Oops three questions actually.  How difficult would it be for EA to find class references to create links between classes?  Any plans for this?  This is what would really be useful.

BTW we built such a tool in the mid eighties in the Tandem environment, and the ability to forward/reverse engineer while picking up references to all objects in the code was truly awesome.  All it took was establishing some solid naming conventions oin advance.  True, however, that if becomes part compiler and less of a simple scanner.

Larry