Formatting Function Names

Related Topics

 

1.    Right-click in the Call Graph, Function List, or Function Detail window, and from the shortcut menu select Method Name, Procedure Name, Function Name. The menu item depends on the programming language you are using.

2.    Select the components you want to include in the function names.

3.    Type the maximum number of characters, up to 75 characters, to appear in names in the call graph.

Notes:

§      The option to limit the number of characters appears only when you display the dialog box from the Call Graph window.

§      Quantify applies function name formatting separately for each window. For example, the function name formatting you select for the Function List window is not automatically applied in the Call Graph and Function Detail windows.

Visual Basic Notes:

§      The Microsoft Visual Basic compiler currently does not encode any information about a procedure's arguments. Consequently, Quantify displays the argument list as (...) in all cases.

§      When profiling 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.FunctionName(...) or DllName.#OrdinalNumber(...).

§      When profiling Visual Basic native-code programs, keep in mind that:

§             The 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, Quantify displays the name as VBHello.HiWorld(...), rather than as MyVBProject.VBHello.HiWorld().

§             Quantify 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(...).

§      If debug symbol data is not available for a procedure, Quantify labels the procedure UnnamedProcedure@<offset> or, in the case of some timed COM procedures, UnnamedTimedProcedure@<offset>. For example, Quantify might display UnnamedTimedProcedure@0x107d38.

(C) Copyright IBM Corporation 1993, 2009.