Late-bound object member references

Late binding is one of the trickier parts in source code analysis. Late binding occurs when you call a procedure or read/write a member variable via an expression whose type is available only at run-time.

Typically, late binding occurs with Variant or Object variables that are used to store object references, or Form variables that store form references. As the type of the object cannot be determined from looking at the code, we cannot reliably detect which class or form the reference goes to. Thus, we must arrange a rule to decide what to do when one is found.

• Ignore late-bound references. If Project Analyzer cannot detect the type of an object expression, it will simply ignore all references to its members. Use this option if the other option doesn't produce good results. Keep in mind that ignoring references may result in extra dead code warnings.
• Accept all syntactically possible references. This is the default option. Project Analyzer carefully examines the code syntax and stores a reference to every possible method or member variable that might come into question. Sometimes this results in references that don't actually happen at run-time. You may also find some extra branches in your call trees. These branches are syntactically possible, but never executed. An example of this could be that 3 classes have a method with the same name, but the variable in question will only hold one of 2 classes in reality. Use this option when detecting dead code in a project with extensive use of late binding or variant/object variables.

You should set this option before starting a new analysis.

Window coordinates

Project Analyzer remembers window positions. Press the Reset button to clear the locations and open new windows at their default positions.

More options