1. Right-click in the Coverage Browser or Function List window and select Method Name, Function Name, or Procedure Name from the shortcut menu.
2. Select the components you want to include in function names.
Notes:
§ The settings you specify apply only to the Function List window.
Visual Basic Notes:
§ The Microsoft Visual Basic compiler currently does not encode any information about a procedure's arguments. Consequently, PureCoverage displays the argument list as (...) in all cases.
§ When monitoring Visual Basic p-code programs, keep in mind that:
§ Procedures defined as Private or that are included in .bas files appear as UnnamedProcedure@<address>, where <address> is the internal address of the procedure entry.
§ Declared procedures appear as DllName.ProcedureName(...) or DllName.#OrdinalNumber(...).
§ When monitoring Visual Basic native-code programs, keep in mind that:
§ 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().
§ 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.