Logtalk 2.43.2 released

Announcements of new Logtalk releases and events

Moderator: Paulo Moura

Post Reply
Paulo Moura
Logtalk developer
Posts: 482
Joined: Sat May 05, 2007 8:35 am
Location: Portugal
Contact:

Logtalk 2.43.2 released

Post by Paulo Moura » Mon Oct 03, 2011 11:02 pm

Hi,

Logtalk 2.43.2 is now available for downloading. This is a minor release with some bug fixes and minor compiler and runtime improvements.


Upgrading from previous release:

* See the "UPGRADING.txt" file and the detailed release notes below for more details.


Known compatibility issues:

* CxProlog 0.97.5: A bug in the implementation of logic database updates results in a failure in the "multifile" unit tests.

* YAP: Some bugs in multi-threading support prevent some thread examples from running. In addition, a bug in the YAP 6.2.1 Windows version prevents its use with Logtalk.

* Ciao Prolog is not currently supported due to the lack of support for stream aliases.


Detailed release notes:

* Optimized the processing of operator declarations when compiling source files and dynamically creating new entities.

* Updated the Logtalk compiler to use the "modules" compiler flag when testing for Prolog module support, thus avoid compilation issues with back-end Prolog compilers that don't support a module system but still define (:)/2 as a built-in control construct or predicate.

* Removed support for the "startup_message" compiler flag "flags(compact)" and "flags(verbose)" values, replaced by a single value, "flags", which corresponds to the old "flags(compact)" value.

* Corrected a bug when using op/3 directives with the create_protocol/3, create_object/4, and create_category/4 built-in predicates where the local operator declarations would be visible outside the new entities.

* Corrected a bug where creating a new dynamic entity at runtime would define a no longer used bookkeeping dynamic predicate that would not be abolished when the entity is abolished.

* Corrected a compiler bug where a "super" call from within an object that only instantiates itself and doesn't specialize any object would throw an exception instead of failing.

* Updated the "benchmarks" example in order to protect against arithmetic exceptions when computing the total number of calls per second for each test. Reduced the number of benchmark test repetitions when running the unit tests to avoid lengthy computing times with slow back-end Prolog compilers.


Happy logtalking,

Paulo
Paulo Moura
Logtalk developer

Post Reply

Who is online

Users browsing this forum: No registered users and 2 guests