Logtalk discussion forums

Hi, Logtalk 3.37.0 is now available for downloading at: https://logtalk.org/ This release adds a new meta-message to the message printing mechanism, allows the "user" pseudo-object to be used as an event monitor, fixes a reflection API bug that could result in duplicated or redundant entity operator...

Hi, Logtalk 3.36.0 is now available for downloading at: https://logtalk.org/ This release adds lint checks for cyclic terms and float comparisons, improves the lint checks for unification goals that are always true or always false, changes the preferred format of dates and versions in "info/1" direc...

Hi, Logtalk 3.35.0 is now available for downloading at: https://logtalk.org/ This release adds a lint check for redefined standard operators, simplifies and improves the compilation and execution performance of meta-calls and lambda expressions, improves compilation of modules as objects for applyin...

The entities in the “types” library form a small hierarchy. Still, check the library notes and also the notes on the “basic_types” library. The later library loads a subset of the types loaded by the “types” hierarchy. If those are enough, then you can replace on your loader file the “logtalk_load(t...

P.S. Until we get a reply from the plug-in author, I suggest you try an alternative to VSC. E.g. Atom (see the coding/atom directory in the Logtalk distribution for details).

Related to your initial question about the warnings when using the VSC Logtalk plug-in:

https://github.com/arthwang/vsc-logtalk/issues/8

Now in the loader files what is the difference between the following two syntaxes? No difference when using logtalk_load/1. Just user preference. But when using logtalk_load/2, the first is used when all loaded files share the same compiler options while the second allows different sets of options ...

Note that loading and usage are separated in Logtalk. Thus, in your loader.lgt file, you will have a directive: :- use_module(library(clpfd)). But in your objects (or categories) where you want to call CLP(FD) predicates using implicit module-qualification, you will need to use the Logtalk use_modul...

You only need to use uses/2 (or use_module/2) directives if you want implicit message sending (or module qualification). Some users like it, other users prefer explicit. Does your application requires you to write the source code of 200 distinct objects, which with their own dependencies in other ob...

Hi, Logtalk 3.34.0 is now available for downloading at: https://logtalk.org/ This release adds support for defining predicate shorthands in "uses/2" and "use_module/2" directives, allows local operators to also be declared in scope directives to simplify compilation of included files, adds support f...

When I go to the VSC tab of the refasModel.lgt file containing my metaclass object definition the Linter warns me: refasModel.lgt:7: Warning: Reference to unknown object: list If I comment line 7 out, the warning then becomes: refasModel.lgt:8: Warning: Reference to unknown object: loop If I in tur...

The uses/2 and use_module/2 directives only declare predicates that will be called, respectively, using implicit message sending or implicit module qualification. Actual loading of the objects or modules referred in those directives must be done in the loader file using logtalk_load/1-2 calls. The u...

You have a typo in line 5:
should be:

Hi, Logtalk 3.33.0 is now available for downloading at: https://logtalk.org/ This release adds make tool support for detecting duplicated library aliases, fixes silent loading of settings files when used to load libraries and tools, updates the documenting tool to list inherited public predicates in...

Hi, Logtalk 3.32.0 is now available for downloading at: https://logtalk.org/ This release adds support for multifile meta-predicates, improves some lint checks, includes fixes and improvements for embedding applications, includes documentation updates and improvements, adds support for storing setti...