Removed flags in Logtalk 3.x

Discussion on migrating applications from Logtalk 2.x to Logtalk 3.x and how to ensure application compatibility with both major versions

Moderator: Paulo Moura

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

Removed flags in Logtalk 3.x

Post by Paulo Moura » Mon Apr 15, 2013 2:16 pm

The following Logtalk 2.x flags are no longer supported in Logtalk 3.x and attempting to use them will result in compiler errors:
  • xmldir, xmldocs, xmlspec, xmlsref, xslfile
  • break_predicate
  • altdirs
  • startup_message
  • smart_compilation
The XML related files were removed as generating documenting files is now the responsibility of the lgtdoc tool. The debugger is also no longer a built-in object but a separate tool, debugger. Logtalk 3.x greatly improves support for source file paths, removing the need for the altdirs flag. The startup_message is removed due to the introduction on structured message printing in Logtalk 3.x, which allows fine grained control over message printing. The smart_compilation flag is no longer necessary and the old behavior can now be controlled using the clean flag.

The reload flag now only controls reloading of a file. In Logtalk 2.x it was mainly used for indirectly allowing static binding but in Logtalk 3.x static binding optimizations now depend only on the optimize flag.

If you use some of the flags listed above in your application and want to keep it compatible with both Logtalk 2.x and Logtalk 3.x, you may be able to use the conditional compilation directives to avoid errors when using Logtalk 3.x. If you need help, post a message in this forum.
Paulo Moura
Logtalk developer

Post Reply

Who is online

Users browsing this forum: No registered users and 1 guest