| |
|
|
|
Glossary
A
A dynamic-link library that lets you automate routine tasks in the Developer Studio environment. 4-2
A way to manipulate an application's objects from outside the application. 7-12
B
A file used by the source code browser and containing information about the symbols in your application. 6-17
C
An open architecture for cross-platform development of client-server applications, based on object-oriented technology. 7-12
Settings for a project. The configuration specifies such things as the type of application to build, target platform, and the settings to use when building, such as compiler and linker options. 6-7
D
A configuration that contains full symbolic debugging information that can be used by the debugger. Typically, no optimization or minimal optimization is used. See also Release configuration. 6-7
A tool that helps you check the logic of an executing program and examine or change variables at run time. 6-19
A window that is docked (attached) along an edge of the visual development environment window and does not have a title bar. 6-6
A set of routines that can be called from procedures that are loaded into your application at run time. 6-3
F
A window that can be moved and has a title bar. 6-6
L
A tool that links one or more object files into an executable. The Developer Studio linker supports incremental linking for faster builds following small changes to the set of source files. 6-2
P
Procedure interface definition
The properties of a procedure, in particular the specifications of the attributes for a function result, the specification of dummy argument attributes, and the information in the procedure heading. 7-13
A tool for determining the execution frequency of various code paths. 6-2
A set of source files required to build an application. Also see Workspace. 6-3
One of seven classifications for projects. Every Visual Fortran project must be one of these seven types. 6-3
R
A configuration that does not contain any symbolic debugging information. It does, however, contain default optimizations or your selected optimizations if you have overridden the defaults. See also Debug configuration. 6-7
Binary data added to an application's executable file. Examples are dialog boxes and icons. 6-5
A tool to help develop user-interface components such as dialog boxes, menus, and icons for your projects. 6-18
S
A tool that lets you look at symbol usage in the source code and view graphs of calling relationships between functions. 6-17
A set of routines that can be called from procedures that are loaded into your application at link time. 6-3
W
The container for one or more projects. The primary workspace file has the extension .dsw. 6-4
| |
|
|
|