logtalk3 icon indicating copy to clipboard operation
logtalk3 copied to clipboard

Logtalk - declarative object-oriented logic programming language

Results 14 logtalk3 issues
Sort by recently updated
recently updated
newest added

I am validating the LogTalk3.5.6.exe application silently , but however I can see below error message during silent installation for the first time. Parameters are used below but still I...

JIProlog 4.1.6.1 and previous versions have a read_term/3 bug when reading the end of file. If the option variable_names/1 is used, its value is not bound by the call. This...

backend prolog compiler bug

Using the Logtalk integration script for GNU Prolog results in predicate existence errors at Logtalk startup: ```text $ gplgt ... warning: /usr/share/logtalk/core/core.pl:25087: user directive caused exception: error(existence_error(procedure,'$lgt_default_flag'/0),'$lgt_cache_compiler_flags'/0) ``` This bug...

backend prolog compiler bug

CxProlog 0.98.2 and previous versions have a `read_term/3` bug when reading the end of file. If the option `variable_names/1` is used, its value is not bound by the call. This...

backend prolog compiler bug

The SWI-Prolog Windows installer starting with version 7.7.20 stop writing registry keys with, notably, the installation directory. The Logtalk Windows installer uses those keys to create the integration shortcut for...

backend prolog compiler bug

A YAP bug in the implementation of the `read_term/2-3` options `variables/1` and `variable_names/1` breaks use of parameter variables. Bug reported to YAP developers at https://github.com/vscosta/yap-6.3/issues/37

backend prolog compiler bug

The B-Prolog 8.1 native random number generator returns random integers, both positive and negative, with no documentation on their range. Given that B-Prolog also claims that its implementation of integer...

backend prolog compiler bug

When a source file contains an atom whose length is larger than 255 characters, B-Prolog 8.1 **apparently** succeeds in loading the file when in fact the file contents fails to...

backend prolog compiler bug

B-Prolog 8.1 atom size limit for interpreted code and for atoms created at runtime (e.g. using `read_term/3`) is 1000 but for compiled code is 255. A consequence is that the...

backend prolog compiler bug

The B-Prolog 8.1 implementation of the standard `sub_atom/5` predicate can return an integer instead a (sub-)atom. For example: ``` | ?- sub_atom('foo#0', 4, _, 0, Atom). Atom = 0 yes...

backend prolog compiler bug