Use the Procedure Name dialog box to determine how PureCoverage displays procedure names for Visual Basic native-code programs.
These are the main controls in the dialog box:
Notes:
§ The settings you specify apply only to the Function List window. The Coverage Browser window always displays module names and argument lists with the procedure names.
§ The Microsoft Visual Basic native-code compiler currently does not:
§ Retain project and sub-project information about procedures. Consequently, if you have a main project called MyVBProject and a sub-project called VBHello, and it defines a procedure called HiWorld, PureCoverage displays the name as VBHello.HiWorld(...), rather than as MyVBProject.VBHello.HiWorld().
§ Encode any information about a procedure's arguments. Consequently, PureCoverage displays the argument list as (...) in all cases.
§ PureCoverage uses the debug information in .pdb files to compose the procedure names it displays. In general, procedure and subroutine names in .frm files appear as Module.procedure(...). Procedures in .bas files appear as Procedure(...).
§ Debug symbol data must be available for PureCoverage to identify a procedure. For some procedures, symbol data is not available from Visual Basic and PureCoverage labels the procedure UnnamedProcedure@<offset>. For example, PureCoverage might display UnnamedProcedure@0x124d.
(C) Copyright IBM Corporation 1993, 2010.