Visual Prolog 10 Upgrade Notes - Revision history

Thomas Linder Puls: predicate name spelling

2026-03-31T08:17:09Z

predicate name spelling

← Older revision		Revision as of 10:17, 31 March 2026
Line 23:		Line 23:
	=== Binary memory representation ===		=== Binary memory representation ===

	Binaries have changed representation. In the old representation a binary was a pointer to the actual data, and immediately before the data the size of the binary was written. Windows API and other external APIs does not use this representation and as a consequence binaries was often had to be copied from the buffer that cntains it to another "buffer" that can hold the size infront of the data. A <vp>binary</vp> is now represented as a pointer to a memory cell containing a pointer to a data-buffer and the size. So the size is no longer placed in a specific place relative to the actual data. With the old representation <vp>uncheckedConvert</vp> of a binary to the <vp>pointer</vp> domain would result in a pointer to the data. With the new representation this is no longer the case and therefore it has been made illegal to <vp>uncheckedConvert</vp> from <vp>binary</vp> to <vp>pointer</vp>, instead you must use <vp>convert</vp> which will both in old and new representation give a pointer to the data. Alternatively, you can use the extension predicate <vp>binary::data()</vp> instead, e.g. <vp>Pointer = MyBinary:~~date~~()</vp>.		Binaries have changed representation. In the old representation a binary was a pointer to the actual data, and immediately before the data the size of the binary was written. Windows API and other external APIs does not use this representation and as a consequence binaries was often had to be copied from the buffer that cntains it to another "buffer" that can hold the size infront of the data. A <vp>binary</vp> is now represented as a pointer to a memory cell containing a pointer to a data-buffer and the size. So the size is no longer placed in a specific place relative to the actual data. With the old representation <vp>uncheckedConvert</vp> of a binary to the <vp>pointer</vp> domain would result in a pointer to the data. With the new representation this is no longer the case and therefore it has been made illegal to <vp>uncheckedConvert</vp> from <vp>binary</vp> to <vp>pointer</vp>, instead you must use <vp>convert</vp> which will both in old and new representation give a pointer to the data. Alternatively, you can use the extension predicate <vp>binary::data()</vp> instead, e.g. <vp>Pointer = MyBinary:data()</vp>.

	=== List comprehension ===		=== List comprehension ===

Thomas Linder Puls: ctrl -> clt

2024-04-18T14:16:03Z

ctrl -> clt

← Older revision		Revision as of 16:16, 18 April 2024
Line 18:		Line 18:
	* '''.frm''' related to forms		* '''.frm''' related to forms
	* '''.win''' related to e.g. the task window		* '''.win''' related to e.g. the task window
	* '''.~~ctrl~~''' related to controls		* '''.ctl''' related to controls
	* '''.dlg''' related to dialogs; '''except''' if it corresponds to "aincient" Visual Prolog 5 resource dialog that has been "inherited" into the project. If in doubt: the code in the corresponding '''.pro''' file of such a dialog will not contain a <vp>generatedInitialize</vp> predicate.		* '''.dlg''' related to dialogs; '''except''' if it corresponds to "aincient" Visual Prolog 5 resource dialog that has been "inherited" into the project. If in doubt: the code in the corresponding '''.pro''' file of such a dialog will not contain a <vp>generatedInitialize</vp> predicate.

Thomas Linder Puls: /* Superfluos files */ plural

2024-01-05T11:41:28Z

Superfluos files: plural

← Older revision		Revision as of 13:41, 5 January 2024
Line 18:		Line 18:
	* '''.frm''' related to forms		* '''.frm''' related to forms
	* '''.win''' related to e.g. the task window		* '''.win''' related to e.g. the task window
	* '''.ctrl''' related to ~~a control~~		* '''.ctrl''' related to controls
	* '''.dlg''' related to dialogs; '''except''' if it corresponds to "aincient" Visual Prolog 5 resource dialog that has been "inherited" into the project. If in doubt: the code in the corresponding '''.pro''' file of such a dialog will not contain a <vp>generatedInitialize</vp> predicate.		* '''.dlg''' related to dialogs; '''except''' if it corresponds to "aincient" Visual Prolog 5 resource dialog that has been "inherited" into the project. If in doubt: the code in the corresponding '''.pro''' file of such a dialog will not contain a <vp>generatedInitialize</vp> predicate.

Thomas Linder Puls: superfluous files

2024-01-05T10:51:56Z

superfluous files

← Older revision		Revision as of 12:51, 5 January 2024
Line 11:		Line 11:

	'''Notice''' it is highly advisable to have a backup of a project before updating.		'''Notice''' it is highly advisable to have a backup of a project before updating.

			=== Superfluos files ===

			The following files are superfluous and should be deleted:

			* '''.frm''' related to forms
			* '''.win''' related to e.g. the task window
			* '''.ctrl''' related to a control
			* '''.dlg''' related to dialogs; '''except''' if it corresponds to "aincient" Visual Prolog 5 resource dialog that has been "inherited" into the project. If in doubt: the code in the corresponding '''.pro''' file of such a dialog will not contain a <vp>generatedInitialize</vp> predicate.

	=== Binary memory representation ===		=== Binary memory representation ===

Thomas Linder Puls: release

2021-04-15T13:50:23Z

release

← Older revision		Revision as of 15:50, 15 April 2021
Line 1:		Line 1:
	~~{{NonReleased}}~~

	This document describes how to upgrade Visual Prolog 9 projects to Visual Prolog 10, for older projects you should also read the [[Visual Prolog 9 Upgrade Notes]].		This document describes how to upgrade Visual Prolog 9 projects to Visual Prolog 10, for older projects you should also read the [[Visual Prolog 9 Upgrade Notes]].

Thomas Linder Puls: Thomas Linder Puls moved page Visual Prolog 10 Release Notes to Visual Prolog 10 Upgrade Notes without leaving a redirect: wrong name

2021-04-14T08:33:29Z

Thomas Linder Puls moved page Visual Prolog 10 Release Notes to Visual Prolog 10 Upgrade Notes without leaving a redirect: wrong name

← Older revision	Revision as of 10:33, 14 April 2021
(No difference)

Thomas Linder Puls: initial

2021-04-14T08:24:44Z

initial

New page

{{NonReleased}}

This document describes how to upgrade Visual Prolog 9 projects to Visual Prolog 10, for older projects you should also read the [[Visual Prolog 9 Upgrade Notes]].

If you have problems with upgrading your projects and need additional information, you are welcome to ask questions in [http://discuss.visual-prolog.com/viewforum.php?f=2 Visual Prolog Discussion Forum].

By default, the installation of Visual Prolog 10 will not replace any previously installed versions. It is possible to work with several versions on a single computer.
* The Commercial Edition will by default be installed in '''C:\Program Files (x86)\Visual Prolog 10''' or '''C:\Program Files\Visual Prolog 10'''.
* The Personal Edition will by default be installed to '''C:\Program Files (x86)\Visual Prolog 10PE''' or '''C:\Program Files\Visual Prolog 10PE'''.

Visual Prolog 10 projects are backward-compatible with Visual Prolog 9 projects.
If you are going to use different versions of Visual Prolog installed at one computer, avoid opening projects by double-clicking on vipprj files.

'''Notice''' it is highly advisable to have a backup of a project before updating.

=== Binary memory representation ===

Binaries have changed representation. In the old representation a binary was a pointer to the actual data, and immediately before the data the size of the binary was written. Windows API and other external APIs does not use this representation and as a consequence binaries was often had to be copied from the buffer that cntains it to another "buffer" that can hold the size infront of the data. A <vp>binary</vp> is now represented as a pointer to a memory cell containing a pointer to a data-buffer and the size. So the size is no longer placed in a specific place relative to the actual data. With the old representation <vp>uncheckedConvert</vp> of a binary to the <vp>pointer</vp> domain would result in a pointer to the data. With the new representation this is no longer the case and therefore it has been made illegal to <vp>uncheckedConvert</vp> from <vp>binary</vp> to <vp>pointer</vp>, instead you must use <vp>convert</vp> which will both in old and new representation give a pointer to the data. Alternatively, you can use the extension predicate <vp>binary::data()</vp> instead, e.g. <vp>Pointer = MyBinary:date()</vp>.

=== List comprehension ===

In a list comprehension <vp>[ Exp || Gen ]</vp> the <vp>Exp</vp> must be a procedure (language reference has always required that, but the compiler has accepted <vp>determ</vp> expressions). In cases where <vp>Exp</vp> is determ the following rewrite can be applied <vp>[ V || Gen, V = Exp ]</vp>.

=== <>_list domains deprecated ===

The domains <vp>integer_list</vp>, <vp>integer_list_list</vp>, etc. has been deprecated. In declarations the *-form should be used, but in predicate calls like <vp>tryToTerm</vp> it is necessary to uses the <vp>list{...}</vp> type constructor, e.g. <vp>tryToTerm(list{integer}, String)</vp>. An old program can require a significant amount of updates.

=== Erroneous predicates as values ===

<vp>erroneous</vp> predicates can now be used as a value, for example in <vp>X otherwise raise_error()</vp>. Hereby <vp>erroneous</vp> functions have become superfluous, and subsequently it is now illegal to declare <vp>erroneous</vp> functions (a corresponding <vp>erroneous</vp> predicate must be used instead).

== See also ==

* [[Visual Prolog 10 New Features]]
* [[Visual Prolog 9 Upgrade Notes]]

[[Category:Release Notes|10 Upgrade Notes]]