Hello Lee!

-------------------------------8<------------------------------------
  5. Integrated Debugger is a source level debugger that uses
     Editor windows to track source:
       - Sophisticated source tracing algorithm that allows
         even complex lines to be stepped over at high speed
         (E.g: for I := 1 to 100000 do SomeFuncCall; )
       - Watches window.
       - Call stack window.
       - Breakpoints window. Besides execution breakpoints
         it's possible to set up to four datapoints (that are
         supported by 386 hardware) with condition and pass
         count.
       - Register window that shows the values of the
         CPU registers and flags and allows to change them.
       - Numeric Coprocessor window with Stack registers, Control
         register and Status register panes that shows the
         state of the 387 coprocessor and lets you change it.
       - Dump window that shows the memory in all Pascal
         integer and floating point formats.
       - CPU window with Code, Data, Register and Stack panes
         displays the source lines and corresponding
         disassembled instructions. You can patch code using
         built-in assembler that is similar to BASM of the VPC.
       - Log window that collects the information about program
         flow (Module loads, thread creations and terminations,
         exceptions, breakpoints, user comments, etc).
       - Evaluate/Modify dialog.
       - Threads dialog lets you examine current program
         threads and freeze or resume them.
       - Exceptions dialog lists all OS/2 system exceptions and
         allows you to specify whether debugger will handle
         particular exception or user program is responsible
         for handling it.
       - Unit dialog lists the units used by the program along
         with the include files. If unit or include file is
         selected, the source file is loaded into editor window.

     IDE can be also used as a high speed assembler level
     debugger.


4. NEW FEATURES
~~~~~~~~~~~~~~~
  1. Compiler has been totally rewritten as 32-bit executable.
     As a result, the 64K limit for the size of code and data
     segments for a single unit and symbol size for a unit
     no longer exists.

  2. Compilation speed has been increased (up to 25%).

  3. Besides dollar symbol ($), the ampersand symbol (&) can be
     used to start compiler directive. You can use it to specify
     Virtual Pascal specific directives: other Pascal
     compilers, such as Borland Pascal, treat them as ordinal
     comments.

  4. All Borland Pascal directives are accepted now. Those
     ones that have no Virtual Pascal equivalents are ignored.
     $A is equivalent to $AlignData.

  5. $Alters directive is introduced. It complements $Saves
     directive.

  6. Smart linking is implemented. Instead of object file(.OBJ),
     compiler can produce object library file (.LIB) for a
     unit. You should NOT use this feature for debugging
     because of the following:
       - library files are larger in size;
       - linking of the units, compiled to object libraries
         can be several times slower than linking object
         files;
       - source level debugging in the IDE is not available for
         the units, compiled to object libraries;

     You may use smart linking for building of the final
     executable. It significantly decreases the size of the
     produced executable file.

  7. Long file names are supported by the run-time library:
       - Size of the file variables has been increased to hold
         long file name;
       - PathStr, DirStr, NameStr, ExtStr, SearchRec types in
         the DOS/WINDOS units has been modified accordingly.

  8. Indices of the dynamic methods are extended to the Longint
     type.

  9. Editor has been significantly improved. The following new
     features have been added:
       - BackSpace unident;
       - BackSpace in overwrite mode does not delete
         characters, but replaces them with blanks;
       - Block Indent/Unindent;
       - Set/Find place marker;
       - Non-Persistent blocks;
       - Delete Word Left (Ctrl-BackSpace)
       - Smart Tab;
       - Pair Matching for () and [];
       - Hide/Display Block works now as a toggle, hiding and
         showing the selected text;
       - PgUp/PgDn does not change cursor position within the
         window;
       - Block Read;
       - Block Write;
       - Incremental search facility;
       - Common clipboard for editor and input line boxes;
       - Print file and Print block commands.


5. IMPORTANT INFORMATION
~~~~~~~~~~~~~~~~~~~~~~~~
  1. Hardware requirements.
     VPC has been written on the PC AT-386DX-40Mhz-4MB of RAM.
     VPC requires PC with at least 386SX processor with 4 MB of
     RAM, but 8MB is strongly recommended (actually, these
     restrictions are not VPC, but OS/2 itself). VPC works
     fine on OS/2 2.1 and OS/2 3.0 Warp. It has not been
     checked on OS/2 2.0, but it should not be any problem.

  2. Linker and Resource Compiler.
     Virtual Pascal doesn't have its own linker and resource
     compiler, so LINK386 and RC shipped with OS/2 are used. If
     you have BC for OS/2 it is also possible to use TLINK (it
     is almost 2-9 times faster than LINK386, but produces
     larger executables) and BRCC (or Resource Workshop).

     Note: In order to use LINK386 and RC you have had to
     install OS/2 with Optional utilities³Link Object Modules
     option enabled.

     Also make sure that linker and resource compiler
     executables are in the directory, mentioned in the PATH
     environment variable.

     It is recommended that the ALIGN, BASE, and EXEPACK
     LINK386 (-A,-B, -Oc TLINK) options be used when linking
     all executables. This will compress them in size and
     improve their performance. Use /ALIGN:4 (/A:4) for 32-bit
     applications. For .EXE files, /BASE:0x10000 (/B:0x10000)
     option must be used to remove internal fixups from
     executable.

     Note, that LINK386 prior to version 2.02.001 (which is
     supplied with OS/2 3.0 Warp) is not able to link
     executable, if more than 32 object libraries are
     specified. If you encounter this problem, look for a new
     version of LINK386 or disable $SmartLink compiler
     directive.

  3. Debug Information.
     Virtual Pascal uses debug information that is recorded
     in the interface information file (.VPI) and doesn't
     support IPMD, BC, CodeView or any other debug information.
     However VPC can put line number information to the object
     file, so for example, if you link it into program written
     in IBM C/C++, you can trace Pascal source in IPMD.

  4. Differences between Virtual Pascal and Borland Pascal 7.0.
     Read VP.TXT file that describes the differences between
     Virtual Pascal and Borland Pascal in detail.

  5. Known problems.
     Hard and soft debugging modes are not yet implemented, so
     when you debug Presentation Manager application you must
     not switch from the IDE to the other sessions.

     Multi-thread support is not yet ready, so switch off stack
     checking {$S-} for multi-thread programs.

  6. What is still not implemented:
       - Variables, Hierarchy and Inspector windows;
       - Breakpoint condition, pass count and action are not
         functioning yet. All breakpoints are unconditional
         and cause program to stop at the breakpoint location;
       - Run³Until return command.

6. LICENSE AGREEMENT
~~~~~~~~~~~~~~~~~~~~
Virtual Pascal is not a freeware product. Virtual Pascal and
programs produced by Virtual Pascal CANNOT be used in a
business, commercial, government or institutional environment
except for evaluation purposes. You may use Virtual Pascal
with the following restrictions:

  1. You may NOT change the Virtual Pascal executables in any
     way.
  2. You may NOT remove or change copyright notice from either
     object, library or executable files produced by Virtual
     Pascal.
  3. You may NOT sell, sublicense, rent, lease, or assign
     Virtual Pascal.
  4. If Virtual Pascal is to be distributed, it should be
     distributed unaltered and in full.
  5. Author can terminate this license at any time.

The usual disclaimers apply, expressed thus:

VIRTUAL PASCAL IS SUPPLIED "AS IS", AND WITHOUT ANY WARRANTIES,
EXPRESS OR IMPLIED, INCLUDING THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.

YOU USE VIRTUAL PASCAL ENTIRELY AT YOUR OWN RISK. AUTHOR WILL
ACCEPT NO LIABILITY FOR ANY LOSS OR DAMAGE INCURRED BY ANYONE
FROM THE USE OR THE PURPORTED USE OF VIRTUAL PASCAL, FOR ANY
PURPOSE WHATSOEVER.

IF YOU USE VIRTUAL PASCAL YOU AGREE TO THESE TERMS.

If these terms are not acceptable to you, then this license is
void: you have no license to use Virtual Pascal and should
delete it from your disk(s).
-------------------------------8<------------------------------------

Bye!
Rinat Sadretdinow                                              [Team BIOS]

--- GoldED/2 2.50.Beta5+