|
Visual Prolog Upgrade Notes
See also:
Upgrading Visual Prolog from 5.1 to 5.2 versionRelease 5.2 of Visual Prolog is almost 100% compatible with the previous 5.1 release. However, if you want to use enhanced possibilities of Visual Prolog 5.2 to handle directories and files, which names include spaces, and to be installed in such directories (e.g. "Program Files"), the scripts in your old projects must be regenerated. Note also that new build script format supports several new VDE features, such as a possibility to specify the stack size for 32-bit Windows applications from the VDE. Cleaning-up OBJ Project Sub-directories.Before upgrading a project, it is necessary to delete contents of .OBJ sub-directory of the project. Regenerating Build ScriptsA special "Warning!" dialog is activated, when you open a Visual Prolog 5.1 project with Visual Prolog 5.2 VDE, to provide you a possibility to regenerate scripts. Be careful, while upgrading your Visual Prolog 5.1 projects into Visual Prolog 5.2 projects, if you are going to return later to Visual Prolog 5.1. Please, read Caution and Converting Visual Prolog 5.2 Projects into Visual Prolog 5.1 Projects. Problems of Upgrading Projects with Borland C as the Main Program for Windows and DOS Platforms.Visual Prolog 5.2 VDE does not support Borland C as Main Program for Windows and DOS Platform. This means that:
Therefore, to use this project with Visual Prolog 5.2, you need to change the Main Program setting to the one supported by this VDE (Prolog or MSVC). When the VDE opens an old project that uses Borland C as "Main Program", the dialog "Warning: Borland C is not Supported" is activated. Upgrading Projects that use Document Handling Package (DOC_TOOL)The structure of the Document Handling package (DOC_TOOL) has been changed in Visual Prolog 5.2. Therefore, in the projects created by previous versions of Visual Prolog that use DOC_TOOL, it is necessary to make manual changes. In the <project_name>.inc file the following lines: include "rtf.con" include "rtf.dom" should be added before include "rtf.pre" Upgrading Projects, in which 590 and 591 Warnings had been Ignored.Since in the versions previous to Visual Prolog 5.2, "590
Nondeterministic clause" and "591 Nondeterministic
predicate" errors were treated as warnings, some user programs that can
be compiled by previous versions of Visual Prolog (if a programmer
ignores the warnings) cannot be compiled with Visual Prolog 5.2. Upgrading One File ProjectsIn Visual Prolog 5.2, the file and db_selector domains have to
be declared as global domains also in a one file project. NoteIf you upgrade you project from Visual Prolog from versions 4.x, 5.0, and 5.02 to Visual Prolog 5.2, please, see also the following pages:
|