Visual Prolog 7.4 New Features - Revision history

Thomas Linder Puls: moved New Features in Visual Prolog 7.4 to Visual Prolog 7.4 New Features

2018-05-14T10:57:56Z

moved New Features in Visual Prolog 7.4 to Visual Prolog 7.4 New Features

← Older revision	Revision as of 12:57, 14 May 2018
(No difference)

Thomas Linder Puls: Category

2018-05-14T10:50:44Z

Thomas Linder Puls: Build 7403

2015-11-24T14:14:27Z

Build 7403

← Older revision		Revision as of 16:14, 24 November 2015
Line 108:		Line 108:

	== Updates ==		== Updates ==

			=== Build 7403 ===

			* PFC: Wrong handling of NULL fields in 64 bit ODBC (gives string right truncation error).
			* IDE: PIE exception in IDE when debugging 64 bit programs

	=== Build 7402 ===		=== Build 7402 ===

Thomas Linder Puls: -

2013-06-04T07:48:58Z

← Older revision		Revision as of 09:48, 4 June 2013
Line 126:		Line 126:
	*Compiler. Incorrect object file if number of fixups exceeds the limit of <vp>0xFFFF</vp> (this could lead to the incorrect state of some statically initialized data, like class facts, etc.).		*Compiler. Incorrect object file if number of fixups exceeds the limit of <vp>0xFFFF</vp> (this could lead to the incorrect state of some statically initialized data, like class facts, etc.).
	*Compiler. Several bugs in 64bit codes generation.		*Compiler. Several bugs in 64bit codes generation.
	*Runtime: Bug in symbol comparison ~~(see )~~.		*Runtime: Bug in symbol comparison.
	*IDE: Browse search shows the same predicate many times.		*IDE: Browse search shows the same predicate many times.
	*Debugger: Several bugs related to the Variables view.		*Debugger: Several bugs related to the Variables view.

Thomas Linder Puls: -

2013-06-04T07:47:16Z

← Older revision		Revision as of 09:47, 4 June 2013
Line 135:		Line 135:
	*VPI: Incorrect behavior of predicate <vp>getText/1-></vp>.		*VPI: Incorrect behavior of predicate <vp>getText/1-></vp>.
	*Vip Linker: It does not accept utf-8 '''.def''' files (see [http://discuss.visual-prolog.com/viewtopic.php?t=9515 Dll - error in file MyDll.def]).		*Vip Linker: It does not accept utf-8 '''.def''' files (see [http://discuss.visual-prolog.com/viewtopic.php?t=9515 Dll - error in file MyDll.def]).

	~~+ Some minor bug fixes~~

	=== Build 7401 ===		=== Build 7401 ===

Thomas Linder Puls: spelling mistake

2013-06-04T07:46:14Z

spelling mistake

← Older revision		Revision as of 09:46, 4 June 2013
Line 115:		Line 115:
	*Compiler. Incorrect handling of some special floating-point constants leads to unexpected compile time errors (see [http://discuss.visual-prolog.com/viewtopic.php?t=9582 Real value 1.#INF is out of the range]).		*Compiler. Incorrect handling of some special floating-point constants leads to unexpected compile time errors (see [http://discuss.visual-prolog.com/viewtopic.php?t=9582 Real value 1.#INF is out of the range]).
	*Compiler. Missing warning for unreachable codes (see [http://discuss.visual-prolog.com/viewtopic.php?t=9569 Unused Variable]).		*Compiler. Missing warning for unreachable codes (see [http://discuss.visual-prolog.com/viewtopic.php?t=9569 Unused Variable]).
	*Compiler. [http://discuss.visual-prolog.com/viewtopic.php?t=9502 Ambiguity in ~~wedBrowserControl~~].		*Compiler. [http://discuss.visual-prolog.com/viewtopic.php?t=9502 Ambiguity in webBrowserControl].
	*Compiler. Codes generation bug for string comparisson (it can lead to access violation exception at runtime in some cases).		*Compiler. Codes generation bug for string comparisson (it can lead to access violation exception at runtime in some cases).
	*Compiler. Nested <vp>if</vp>-<vp>then</vp>-<vp>else</vp> expressions can raise unexpected error messages related to the wrong flow patterns.		*Compiler. Nested <vp>if</vp>-<vp>then</vp>-<vp>else</vp> expressions can raise unexpected error messages related to the wrong flow patterns.

Alexander Doronin: /* Build 7402 */

2013-06-04T04:35:02Z

Build 7402

← Older revision		Revision as of 06:35, 4 June 2013
Line 126:		Line 126:
	*Compiler. Incorrect object file if number of fixups exceeds the limit of <vp>0xFFFF</vp> (this could lead to the incorrect state of some statically initialized data, like class facts, etc.).		*Compiler. Incorrect object file if number of fixups exceeds the limit of <vp>0xFFFF</vp> (this could lead to the incorrect state of some statically initialized data, like class facts, etc.).
	*Compiler. Several bugs in 64bit codes generation.		*Compiler. Several bugs in 64bit codes generation.
			*Runtime: Bug in symbol comparison (see ).
			*IDE: Browse search shows the same predicate many times.
			*Debugger: Several bugs related to the Variables view.
			*Debugger: Some problems in single step in if-then-else expression.
			*PFC: [http://discuss.visual-prolog.com/viewtopic.php?t=9565 Bug in arrayM_boolean].
			*PFC: Some keywords coloring (see [http://discuss.visual-prolog.com/viewtopic.php?t=9610 Cosmetic detail : <vp>guard</vp>]).
			*PFC: Some problems with handling of enter/leave mouse event.
			*VPI: Incorrect behavior of predicate <vp>getText/1-></vp>.
			*Vip Linker: It does not accept utf-8 '''.def''' files (see [http://discuss.visual-prolog.com/viewtopic.php?t=9515 Dll - error in file MyDll.def]).

	+ Some minor bug fixes		+ Some minor bug fixes

Alexander Doronin: /* Build 7402 */

2013-06-04T04:23:45Z

Build 7402

← Older revision		Revision as of 06:23, 4 June 2013
Line 117:		Line 117:
	*Compiler. [http://discuss.visual-prolog.com/viewtopic.php?t=9502 Ambiguity in wedBrowserControl].		*Compiler. [http://discuss.visual-prolog.com/viewtopic.php?t=9502 Ambiguity in wedBrowserControl].
	*Compiler. Codes generation bug for string comparisson (it can lead to access violation exception at runtime in some cases).		*Compiler. Codes generation bug for string comparisson (it can lead to access violation exception at runtime in some cases).
	*Compiler. Nested ~~'''~~if-then-else~~'''~~ expressions can raise unexpected error messages related to the wrong flow patterns.		*Compiler. Nested <vp>if</vp>-<vp>then</vp>-<vp>else</vp> expressions can raise unexpected error messages related to the wrong flow patterns.
	*Compiler. Unexpected error message for supported interface and inherited class conflict for a generic scope.		*Compiler. Unexpected error message for supported interface and inherited class conflict for a generic scope.
	*Compiler. No error if constructor is absent for an object class with ''noDefaultConstructor'' attribute.		*Compiler. No error if constructor is absent for an object class with <vp>noDefaultConstructor</vp> attribute.
	*Compiler. Incorrect warning c231 (scope is opened but not used) in some cases.		*Compiler. Incorrect warning c231 (scope is opened but not used) in some cases.
	*Compiler. Code generation bug for nested ~~'''~~finally~~'''~~ statements with cuts in ~~'''~~try~~'''~~ part (this could could lead to exceptions at runtime in some cases).		*Compiler. Code generation bug for nested <vp>finally</vp> statements with cuts in the <vp>try</vp> part (this could could lead to exceptions at runtime in some cases).
	*Compiler. Code generation bug for read-only property implemented by a clause with several heads.		*Compiler. Code generation bug for read-only property implemented by a clause with several heads.
	*Compiler. Anonymous predicates in both ''xxx'' as function and ''xxx'' as predicate give declaration conflict.		*Compiler. Anonymous predicates in both ''xxx'' as function and ''xxx'' as predicate give declaration conflict.
	*Compiler. Incorrect object file if number of fixups exceeds the limit of ~~oxFFFF~~ (this could lead to the incorrect state of some statically initialized data, like class facts, etc.).		*Compiler. Incorrect object file if number of fixups exceeds the limit of <vp>0xFFFF</vp> (this could lead to the incorrect state of some statically initialized data, like class facts, etc.).
	*Compiler. Several bugs in 64bit codes generation.		*Compiler. Several bugs in 64bit codes generation.

Alexander Doronin: /* Build 7402 */

2013-06-04T04:17:40Z

Build 7402

← Older revision		Revision as of 06:17, 4 June 2013
Line 113:		Line 113:
	Important bug fixes:		Important bug fixes:

	*Compiler. Incorrect handling of some special floating-point constants leads to unexpected compile time errors (see [http://discuss.visual-prolog.com/viewtopic.php?t=9582]).		*Compiler. Incorrect handling of some special floating-point constants leads to unexpected compile time errors (see [http://discuss.visual-prolog.com/viewtopic.php?t=9582 Real value 1.#INF is out of the range]).
	*Compiler. Missing warning for unreachable codes (see [http://discuss.visual-prolog.com/viewtopic.php?t=9569]).		*Compiler. Missing warning for unreachable codes (see [http://discuss.visual-prolog.com/viewtopic.php?t=9569 Unused Variable]).
	*Compiler. ~~Ambiguity in wedBrowserControl (see~~ [http://discuss.visual-prolog.com/viewtopic.php?t=9502]).		*Compiler. [http://discuss.visual-prolog.com/viewtopic.php?t=9502 Ambiguity in wedBrowserControl].
	*Compiler. Codes generation bug for string comparisson (it can lead to access violation exception at runtime in some cases).		*Compiler. Codes generation bug for string comparisson (it can lead to access violation exception at runtime in some cases).
	*Compiler. Nested '''if-then-else''' expressions can raise unexpected error messages related to the wrong flow patterns.		*Compiler. Nested '''if-then-else''' expressions can raise unexpected error messages related to the wrong flow patterns.

Alexander Doronin: /* Build 7402 */

2013-06-04T04:12:17Z

Build 7402

← Older revision		Revision as of 06:12, 4 June 2013
Line 111:		Line 111:
	=== Build 7402 ===		=== Build 7402 ===

	~~The following new feature has been implemented~~:		Important bug fixes:

	~~Important~~ bug ~~fixes:~~		*Compiler. Incorrect handling of some special floating-point constants leads to unexpected compile time errors (see [http://discuss.visual-prolog.com/viewtopic.php?t=9582]).
			*Compiler. Missing warning for unreachable codes (see [http://discuss.visual-prolog.com/viewtopic.php?t=9569]).
			*Compiler. Ambiguity in wedBrowserControl (see [http://discuss.visual-prolog.com/viewtopic.php?t=9502]).
			*Compiler. Codes generation bug for string comparisson (it can lead to access violation exception at runtime in some cases).
			*Compiler. Nested '''if-then-else''' expressions can raise unexpected error messages related to the wrong flow patterns.
			*Compiler. Unexpected error message for supported interface and inherited class conflict for a generic scope.
			*Compiler. No error if constructor is absent for an object class with ''noDefaultConstructor'' attribute.
			*Compiler. Incorrect warning c231 (scope is opened but not used) in some cases.
			*Compiler. Code generation bug for nested '''finally''' statements with cuts in '''try''' part (this could could lead to exceptions at runtime in some cases).
			*Compiler. Code generation bug for read-only property implemented by a clause with several heads.
			*Compiler. Anonymous predicates in both ''xxx'' as function and ''xxx'' as predicate give declaration conflict.
			*Compiler. Incorrect object file if number of fixups exceeds the limit of oxFFFF (this could lead to the incorrect state of some statically initialized data, like class facts, etc.).
			*Compiler. Several bugs in 64bit codes generation.

	+ Some minor bug fixes		+ Some minor bug fixes

← Older revision		Revision as of 12:50, 14 May 2018
Line 162:		Line 162:
	* [[Visual Prolog 7.4 Upgrade Notes]]		* [[Visual Prolog 7.4 Upgrade Notes]]

	[[Category:Release Notes]]		[[Category:Release Notes\|7.4 New Features]]