Generate .MAP files
This instructs the VO linker to create .MAP files when EXEs/DLLs are created. The .MAP files contain structure and load information about the binary file produced. Part of a .MAP file is shown below:
Application 3
Timestamp is 3d6eb169 (Fri Aug 30 09:42:33 2002)
Preferred load address is 400000
Start Length Name Class
0001:00000000 000618e4H .text CODE
0002:00000000 00009334H .data DATA
0003:00000000 000073ecH .idata DATA
0004:00000000 00005478H .reloc DATA
0005:00000000 000b5914H .rsrc DATA
Address Publics by Value Rva+Base Lib:Object
0001:00000038 EMPTYSHELLMENU_ACCELERATOR:INIT 00401038 f (0x03D000C0)<Application 3:Standard Menus>
0001:000001ac EMPTYSHELLMENU:INIT 004011ac f (0x03D000C9)<Application 3:Standard Menus>
No exception handler
The VO runtime normally intercepts any exception that occurs when an application is running and displays an error dialog saying "This program has performed an illegal operation and will be shut down.". The appearance of this error dialog is controlled by the No exception handler setting - putting a checkmark in this box will disable the VO exception handler.
This setting can be useful if you are using a JIT (Just-In-Time) debugger, such as the GoVest debugger discussed in Software Development Techniques magazine (issue 1999/03). If the VO exception handler is enabled the error is not passed through to the JIT debugger.
Default array borders
This setting determines how arrays are displayed in the debugger.
Maximum history entries for expressions
The debugger allows you to evaluate expressions and VO maintains a list of those expressions. This setting lets you alter the number of entries in that list.