Old Logtalk discussion forums - read-only

Hi, The discussion forums are moving to GitHub: https://github.com/LogtalkDotOrg/logtalk3/discussions The contents of the old discussion forums (at https://forums.logtalk.org/) cannot and will not be transferred, however, and will continue to be accessible using the same URL. For all intents and pur...

Hi, Logtalk 3.43.0 is now available for downloading at: https://logtalk.org/ This release focus once again on improved testing support and improved test suites for both Logtalk features and Prolog standards compliance of supported backends. It also provides compiler improvements and bug fixes, provi...

Fixed in the current Logtalk git version: https://github.com/LogtalkDotOrg/logtalk3/commit/1b66dcac4f4d99428fdad2fc40e5290a6be0d0f4 Thanks for reporting. P.S. In the loader file, there's no point in trying to compile the "meta", "types", and "debugger" libraries in debug mode as their loader files o...

A know incompatibility is due to the use of SWI-Prolog eager evaluation of dict functions, which can result in errors due to arguments only know at runtime. No workaround exists currently. There are likely others such as the one that's causing the issue you report. For code portability, proprietary ...

The debug(on) option is only affecting the compilation of the "my_types" source file. It also affects the compilation of the loader files themselves for libraries and tools but not the actual source files loaded by the loader files. I.e. the "my_types" category is the only entity compiled in debug m...

I'm unable to reproduce the problem. The query works for me outside the debugger: ?- {types(loader), meta(loader), my_types}. ... % (0 warnings) true. ?- R = _{a:[ _{impact:5, risk:50, asset:_{id:"1", os:"linux", ip:"1.1.1.1"}, type:"dos", id:"1"}, _{impact:5, risk:50, asset:_{id:"2", os:"linux", ip...

Hi, Logtalk 3.42.0 is now available for downloading at: https://logtalk.org/ This release focus on improved testing support and improved test suites for both Logtalk features and Prolog standards compliance of supported backends. It also adds new "logtalk_load_context/2" predicate keys, generalizes ...

This raises the following questions: - How to deal with the category imports and the inheritance hierarchies when serializing an object? Should we just add a SWI-Prolog dictionary / JSON key-value pair for every imported and inherited clauses of a Logtalk object into its serialization? Is exchangin...

The library "type" object provides building blocks for type-checking predicate arguments: https://logtalk.org/manuals/libraries/types.html https://logtalk.org/library/type_0.html Another option, using the type-checking predicates mentioned above, is to use the events and monitors to watch for messag...

Hi, Logtalk 3.41.0 is now available for downloading at: https://logtalk.org/ This release adds new linter checks for tautologies and falsehoods, adds a new convenience error throwing built-in method for uninstantiation errors, provides updated support for Tau Prolog, provides library fixes for Quint...

1. Is there a more elegant solution to include http server functionality within Logtalk? The issue you found is caused by the Logtalk message sending control construct, ::/2, being handled as a predicate by (SWI-)Prolog and thus not being correctly processed when used as a closure in the http_handl...

Prolog systems map a thread to a POSIX thread (or a POSIX thread emulation on Windows operating-systems). These are sometimes referred to as "heavy" threads. I'm not really familiar with Erlang but my understanding is that Erlang threads, sometimes called "green" threads, are much more light-weight ...

Logtalk threaded engine predicates can also be used when running with ECLiPSe (which is also open source) as the backend.

Logtalk multi-threading features requires a backend Prolog system implementing the ISO draft proposal for threads. The only systems doing it and doing reliably are ECLiPSe and SWI-Prolog (but the lack of a few key predicates means that ECLiPSe can only run the multi-threading engines examples, not t...

This have been discussed a few times in the past. I once made a proposal for standardizing Prolog foreign language interfaces at the Prolog Common initiative. But there was no followup and the Prolog Common initiative eventually died. Only a few Prolog backends provide a sockets interface. There's n...