eclipse-clp-users — ECLiPSe Users List

[eclipse-clp-users] Logtalk 3.92.0 released

[Paulo M. <pm...@lo...>]

Hi,

Logtalk 3.92.0 is now available for downloading at:

https://logtalk.org/

This release fixes bugs in the implementation of the "asserta/1-2" and "clause/2" built-in methods; consolidates Handbook, APIs documentation, and man pages in a "docs" directory; adds new glossary entries to the Handbook; improves Handbook documentation on performance and on writing multi-threading applications; improves the "lgtunit" tool documentation on timing tests; adds a new "json_lines" library implementing the JSON Lines standard proposal; provides improved "packs" tool support for experimental and deprecated packs; updates the "packs" tool "update/2-3" predicates to allow restricting the required status for pack updates; improves several examples, notably the multi-threading examples; updates the release build script to include the APIs documentation in the manuals archive; updates the portable Docker image to include the JAR files required by the Java examples; and includes examples portability updates for SWI-Prolog, Trealla Prolog, and XVM.

For details and a complete list of changes, please consult the release notes at:

https://github.com/LogtalkDotOrg/logtalk3/blob/master/RELEASE_NOTES.md

You can show your support for Logtalk continued development and success at GitHub by giving us a star and a symbolic sponsorship:

https://github.com/LogtalkDotOrg/logtalk3

Happy logtalking!  
Paulo


-----------------------------------------------------------------
Paulo Moura
Logtalk developer

[eclipse-clp-users] Logtalk 3.90.0, Logtalk for VSCode 0.39.0, Jupyter Kernel for Logtalk 0.29.0, and portable Docker image releases

[Paulo M. <pm...@lo...>]

Hi,

Logtalk 3.90.0 is now available for downloading at:

https://logtalk.org/

This release provides fixes and improvements to the Bash and PowerShell scripts used for backend integration, embedding, tools, Docker images, releases, and installation; adds support for generating single file versions of the Handbook and APIs documentation in LLM friendly Markdown format; adds new predicates to the "random" and "types" libraries; adds new "apache_poi" and "lips" programming examples; and fixes a VSCode code navigation issue with single references to local predicates.

For details and a complete list of changes, please consult the release notes at:

https://github.com/LogtalkDotOrg/logtalk3/blob/master/RELEASE_NOTES.md


Logtalk for VSCode 0.39.0 is now available from both VSCode and VSCodium marketplaces:

https://marketplace.visualstudio.com/items?itemName=LogtalkDotOrg.logtalk-for-vscode
https://open-vsx.org/extension/LogtalkDotOrg/logtalk-for-vscode

Requires Logtalk 3.87.0 or a later version (3.90.0 recommended).

Recent changes (since 0.33.0):

* Added source information to diagnostics
* Provided a menu with the valid choices for the backend setting instead of requiring typing it
* Improved readme section on settings
* Updated author information in the license file
* Updated the documentation on the code navigation features
* Updated readme section on "Go To References" support
* Fixed most spurious find definition queries when pressing the Command (macOS) or Control (Windows, Linux) keys with the cursor over some random (but not selected) text


Jupyter Kernel for Logtalk 0.29.0 published, available from both PyPI and Conda registries:

https://pypi.org/project/logtalk-jupyter-kernel/
https://anaconda.org/conda-forge/logtalk-jupyter-kernel

Recent changes (since 0.16.0): 

* Added "%%csv file.csv" and "%%tsv file.tsv" cell magics to print a table but also save it to CSV/TSV files
* Added "%%data" cell magic for data visualization using the Python `matplotlib` package
* Updated the the kernel overview notebook with a section on data visualization
* Fixed saving queries
* Fixed the print table predicates when query variables unify but not become bound to a non-variable term
* Fixed kernel crash when using an invalid variable reference


Docker image with Logtalk, Prolog systems, and Jupyter updated and available:

https://hub.docker.com/r/logtalk/logtalk3-portable/tags


You can show your support for Logtalk continued development and success at GitHub by giving us a star and a symbolic sponsorship:

https://github.com/LogtalkDotOrg/logtalk3


Enjoy,
Paulo


-----------------------------------------------------------------
Paulo Moura
Logtalk developer

[eclipse-clp-users] Logtalk 3.89.0, Logtalk for VSCode 0.33.0, Jupyter Kernel for Logtalk 0.16.0, and portable Docker image releases

[Paulo M. <pm...@lo...>]

Hi,

Logtalk 3.89.0 is now available for downloading at:

https://logtalk.org/

This release adds new glossary entires; update the developer tools documentation on requirements; improves the "packs" tool handling of failed pack archive downloads; update the "diagrams" tool for the new d2 0.6.9 release; adds a new example, "jupyter", illustrating how to write source files that can be interpreted as scripts and open as Jupyter notebooks; improves the instructions on how to run the examples documentation as Jupyter notebooks; includes multiple improvements and fixes to examples documentation for a better experience when open as notebooks; includes fixes and improvements for the portable Docker image; improves portability of the embedding and release scripts; and includes examples portability updates for Trealla Prolog and XVM.

For details and a complete list of changes, please consult the release notes at:

https://github.com/LogtalkDotOrg/logtalk3/blob/master/RELEASE_NOTES.md


Logtalk for VSCode 0.33.0 is now available from both VSCode and VSCodium marketplaces:

https://marketplace.visualstudio.com/items?itemName=LogtalkDotOrg.logtalk-for-vscode

https://open-vsx.org/extension/LogtalkDotOrg/logtalk-for-vscode

Requires Logtalk 3.87.0 or later and a supported Prolog backend.

Changes:

* Adds "Logtalk: Jupyter" commands (requires Juyptext 1.16.7 or later version)
* Provides a menu with the valid choices for the backend setting instead of requiring typing it

https://github.com/LogtalkDotOrg/logtalk-for-vscode/releases/tag/v0.33.0


Jupyter Kernel for Logtalk 0.16.0 published with documentation updates.


Docker image with Logtalk, Prolog systems, and Jupyter available:

https://hub.docker.com/r/logtalk/logtalk3-portable/tags

Includes:

* Logtalk 3.89.0
* B-Prolog 8.1
* Ciao Prolog 1.23.0-m1
* CxProlog 0.98.3
* ECLiPSe 7.1#13
* GNU Prolog latest git master version
* SWI-Prolog latest git master version
* Trealla Prolog latest git main version
* XSB latest git git-origin version
* YAP latest git master version
* Dependencies for the Logtalk developer tools
* Latest Jupyter version


You can show your support for Logtalk continued development and success at GitHub by giving us a star and a symbolic sponsorship:

https://github.com/LogtalkDotOrg/logtalk3

Happy logtalking!
Paulo

-----------------------------------------------------------------
Paulo Moura
Logtalk developer

[eclipse-clp-users] Logtalk 3.87.0 and Logtalk for VSCode 0.32.0 released

[Paulo M. <pm...@lo...>]

Hi,

Logtalk 3.87.0 is now available for downloading at:

https://logtalk.org/

This release adds new loaded file properties to the reflection API; updates the documentation on integration scripts and developer tool requirements; removes deprecated tool JScript scripts; fixes a bug in the `lgtenv.ps1` PowerShell script; adds additional tests for the Prolog standard all-solution meta-predicates; and improves the support for VSCode and VSCodium.

For details and a complete list of changes, please consult the release notes at:

https://github.com/LogtalkDotOrg/logtalk3/blob/master/RELEASE_NOTES.md


Logtalk for VSCode 0.32.0 is now available from both VSCode and VSCodium marketplaces:

https://marketplace.visualstudio.com/items?itemName=LogtalkDotOrg.logtalk-for-vscode

https://open-vsx.org/extension/LogtalkDotOrg/logtalk-for-vscode

Requires Logtalk 3.87.0 or a later version.

Recent changes (since 0.29.0):

- Add support for re-running a single test using CodeLens
- Fix case where
duplicated items could be created in the "PROBLEMS" pane
- Fix "Logtalk: Toggle Code Lens" command to preserve code lens outdated status
- Fix code navigation issues on Windows
- Fix code navigation false warnings of code not loaded on Windows


You can show your support for Logtalk continued development and success at GitHub by giving us a star and a symbolic sponsorship:

https://github.com/LogtalkDotOrg/logtalk3


Enjoy,
Paulo

-----------------------------------------------------------------
Paulo Moura
Logtalk developer

[eclipse-clp-users] Advent of Code 2024 in ECLiPSe-CLP

[<ms...@an...>]

I did the "Advent of Code" challenge in ECLiPSe-CLP and posted my
solutions and some commentary here:
   https://northcoastsynthesis.com/news/aoc-2024/

Maybe it'll be of interest to other users.

-- 
Matthew Skala
ms...@an...                 People before tribes.
https://ansuz.sooke.bc.ca/

[eclipse-clp-users] Logtalk 3.86.0 and Logtalk for VSCode 0.29.0 releases

[Paulo M. <pm...@lo...>]

Hi,

Logtalk 3.86.0 is now available for downloading at:

https://logtalk.org/

This release adds an experimental "logtalk::message_prefix_file/6" hook predicate to the message printing mechanism; fixes case where a false positive left-recursion linter warning would be printed; fixes several grammar and spelling typos in the documentation; changes the The "lgtunit" tool test compilation warning and error messages for better integration with other developer tools; adds experimental "diagrams" tool support for the d2 graph language; updates the "diagrams" tool to support additional text editors when generating diagrams with links to local files; updates the "diagrams" tool to use a Unicode glyph for the zoom icon instead of an image file; fixs a bug in the "lgtdoc" tool when printing a warning on missing entity directive "info/1" keys; updates the "tutor" tool to explain additional linter warnings; updates the "tutor" tool to support displaying warnings and errors augmented with explanations in VSCode; adds a new benchmarks example contributed by Paul Tarau; adds additional Prolog standards compliance tests; improves installation instructions; updates the VSCode support to also list the "lgtunit" tool warning and error messages in the "PROBLEMS" pane; and provides portability updates for Ciao Prolog and XSB.

For details and a complete list of changes, please consult the release notes at:

https://github.com/LogtalkDotOrg/logtalk3/blob/master/RELEASE_NOTES.md


Logtalk for VSCode 0.29.0 is now available from both VSCode and VSCodium marketplaces:

https://marketplace.visualstudio.com/items?itemName=LogtalkDotOrg.logtalk-for-vscode

https://open-vsx.org/extension/LogtalkDotOrg/logtalk-for-vscode

Recent changes (sing 0.26.0):

- Label file tests and metrics data displayed using CodeLens as possibly outdated when editing the file
- Display tutor tool explanations in the "PROBLEMS" pane
- Fix reporting of failed tests when re-running tests
- Improve description of project (workspace) commands
- Fix code navigation issues when defining only the required settings


You can show your support for Logtalk continued development and success at GitHub by giving us a star and a symbolic sponsorship:

https://github.com/LogtalkDotOrg/logtalk3


Enjoy,
Paulo

-----------------------------------------------------------------
Paulo Moura
Logtalk developer

[eclipse-clp-users] Logtalk 3.85.0 released

[Paulo M. <pm...@lo...>]

Hi,

Logtalk 3.85.0 is now available for downloading at:

https://logtalk.org/

This release adds a "linter" meta-flag to allow turning on/off all linter warnings; adds new "encodings" and "general" linter flags; converts some linter warnings into compilation errors; adds a new linter check for redundant entity qualification in predicate directives; changes the "logtalk_load_context/2" built-in predicate to type-check the key argument; improves error-checking for the "use_module/1-2", "export/1", and "reexport/2" directives; fixes a regression in the previous release that prevented reloading code after fixing compilation errors without restarting the current session; improves the documentation of the "issue_creator" tool; improves the Handbook sections on performance and meta-predicates; improves the Handbook documentation on the "logtalk_make/0-1" built-in predicates; updates the "meta_compiler" library to support optimization of meta-calls with closure meta-arguments that are messages to parametric objects; adds "diagrams" tool support for generating diagrams with local links to source file and directories that open in selected text editors; updates the "tutor" tool to explain additional compiler and developer tools warnings and errors; fixes harmless repeated warning in the "packs" tool when pack dependencies are not available; includes improvements and portability fixes to some examples; adds new tests and improves existing tests for Logtalk and standard Prolog features; and updates embedding scripts to accept an optional startup application goal argument.

For details and a complete list of changes, please consult the release notes at:

https://github.com/LogtalkDotOrg/logtalk3/blob/master/RELEASE_NOTES.md

You can show your support for Logtalk continued development and success at GitHub by giving us a star and a symbolic sponsorship:

https://github.com/LogtalkDotOrg/logtalk3

Happy logtalking!  
Paulo

-----------------------------------------------------------------
Paulo Moura
Logtalk developer

[eclipse-clp-users] Logtalk 3.84.0 released

[Paulo M. <pm...@lo...>]

Hi,

Logtalk 3.84.0 is now available for downloading at:

https://logtalk.org/

This release improves the compiler to detect and report recursive references to files and entities; fixes the compiler to prevent using grammar rules to try to redefine disjunction and conditional control constructs; improves the Handbook glossary; improves the documentation of the "logtalk_tester" script; improves the documentation of the "help", "lgtdoc", "packs" tools; adds new directory deletion predicates to the "os" library; improves the "hook_flows" library; includes improved documentation and additional tests for the "dictionaries" library; fixes "meta_compiler" library issues; adds "lgtunit" tool support for running just a selection of tests; adds "packs" tool support for installing and updating packs from local archives, for "gpg" encrypted pack and registry archives, for using "wget" in alternative to "curl", and for for using ".sig" signature files in alternative to ".asc" signature files; adds "tutor" tool support for explaining selected "lgtunit", "make", and "packs" tool error messages; fixes the "dead_code_scanner" tool to avoid some false positives; fixes the "logtalk_tester" script to follow symbolic links when looking for test driver files; adds an example of defining a DSL for tests; adds additional tests for Prolog standard and de facto standard predicates; improves tests coverage for the "dead_code_scanner" and "packs" tools; and provides portability updates for SWI-Prolog and YAP. Thanks to Alex Kouznetsov, Michael McNally, and Lindsey Spratt for their contributions to this release.

For details and a complete list of changes, please consult the release notes at:

https://github.com/LogtalkDotOrg/logtalk3/blob/master/RELEASE_NOTES.md

You can show your support for Logtalk continued development and success at GitHub by giving us a star and a symbolic sponsorship:

https://github.com/LogtalkDotOrg/logtalk3

Happy logtalking!
Paulo

-----------------------------------------------------------------
Paulo Moura
Logtalk developer

Re: [eclipse-clp-users] set_flag(after_event_timer, virtual) on Linux

[Joachim S. <jsc...@co...>]

Hi Chris,

thanks for your feedback. Indeed, the documentation is not up to date in places 
here!

With the introduction of multithreading in version 7.0, the *after*-event 
functionality was completely reimplemented. It previously relied on Unix signal 
handling, but is now portably built on top of a timer-thread (both on Windows 
and Unix). Unfortunately, that meant the loss of the capability to choose 
between real and virtual/cpu time (which was supported on Unix previously).

There is at the moment no portable way of basing an event on CPU time directly.  
You could build something approximate by using real time events and then looking 
at CPU time in the handler. The relevant facilities in versions 7.x are:

  * after-events
    <http://eclipseclp.org/doc/bips/kernel/event/event_after-2.html> (see
    event_after/2, event_after_every/2 etc):
      o real (wall clock) time based
      o thread safe, affect only the calling thread
  * lib(timeout) <http://eclipseclp.org/doc/bips/lib/timeout/index.html>: based
    on after-events, same properties
  * cputime(T) <http://eclipseclp.org/doc/bips/kernel/opsys/cputime-1.html> and
    statistics(cputime, T): retrieve the cpu time of the calling thread (will be
    less than elapsed real time)
  * statistics(times, [T,_,_])
    <http://eclipseclp.org/doc/bips/kernel/env/statistics-2.html>: gives the cpu
    time for the whole process, i.e. the sum of all thread cpu times (may be
    more than elapsed real time)


Having said that, on Unix platforms it is still possible to raise an event based 
on (process) CPU time, by using set_interrupt_handler/2 
<http://eclipseclp.org/doc/bips/kernel/event/set_interrupt_handler-2.html> and 
the deprecated set_timer/2 
<http://eclipseclp.org/doc/bips/kernel/obsolete/set_timer-2.html>, for example:

    ?- set_interrupt_handler(vtalrm, throw/1).
    Yes (0.00s cpu)

    ?- set_timer(virtual, 3), catch((repeat,fail), vtalrm, writeln("Timed out")).
    Timed out
    Yes (3.00s cpu)

The problem with this (and the reason set_timer/2 was deprecated) is that

  * it's not supported on Windows
  * it's uses total process (rather than per-thread) CPU time
  * the event is posted only to the thread that called set_interrupt_handler/2

I can see that it would be useful to have a variant of after-events triggered by 
the exhaustion of a CPU time allocation, or even other resource limits!

Further comments inline below...


On 24/09/2024 21:54, Chris Meudec wrote:
> HI,
> I am using ECLiPSe 7.1 on Ubuntu, and using after events for the first time.
>
> all is well except that the flag after_event_timer is set on "real" timer by 
> default which I take to be "real time elapsed since the start of the ECLiPSe 
> session" in other words wall-time which does not represent processing time (or 
> cpu time) due to OS scheduling.
>
> When in Linux  (Ubuntu 24.04) I do:
>
> set_flag(after_event_timer, virtual). %causes out of range when set to virtual 
> (what I need I think) but is ok for real: checked in tkeclipse and from CLI
>
> So it looks like it is no longer available in Linux either.

Yes, sorry, should have been mentioned in the release notes and documentation 
more properly sanitised...


> It's no big deal, I think, but it will introduce variability in execution 
> making some results hard to reproduce as I use after events to abort (via an 
> exception) some of my optimisation problems searches.

Yes, that is a clear use case.


>
> Also the documentation says: "In addition, the users should not make use of 
> these timers for their own purposes if they plan to use the after event 
> mechanism." in last sentence of paragraph 14.1.2 which I do not understand.

This warning no longer applies - after events no longer rely on timers.


>
> I would like to set an after event that is associated with user cputime to 
> avoid variations between runs: is that possible in Linux?
>
> And although I am not quite there yet, if and when I do move to using Engine 
> and Threads I am right to assume that every thread (engine?) will use its own 
> 'real' time (assuming cpu time is not available)?

The real/wall/elapsed time is a single shared clock, but every thread has its 
own CPU time, as measured by cputime/1.


>
> Thanks for the support.
> Chris
> --
> Dr Chris Meudec <http://www.echancrure.eu/> (he/him) Maitrise, PhD, MA (T&L)
> Lecturer in Software Development
> South East Technological University - Carlow Campus - Ireland
> E chr...@se... <mailto:chr...@se...> |  *setu.ie 
> <https://setu.ie/>*
> turn on images <https://setu.ie/>
>
> Kilkenny Road Campus, Kilkenny Road, Carlow, R93 V960, Ireland
> Campas Bhóthar Chill Chainnigh, Bóthar Chill Chainnigh, Ceatharlach, R93 V960, 
> Éire
>

[eclipse-clp-users] set_flag(after_event_timer, virtual) on Linux

[Chris M. <Chr...@se...>]

HI,
I am using ECLiPSe 7.1 on Ubuntu, and using after events for the first time.

all is well except that the flag after_event_timer is set on "real" timer by default which I take to be "real time elapsed since the start of the ECLiPSe session" in other words wall-time which does not represent processing time (or cpu time) due to OS scheduling.

When in Linux  (Ubuntu 24.04) I do:

set_flag(after_event_timer, virtual). %causes out of range when set to virtual (what I need I think) but is ok for real: checked in tkeclipse and from CLI

So it looks like it is no longer available in Linux either. It's no big deal, I think, but it will introduce variability in execution making some results hard to reproduce as I use after events to abort (via an exception) some of my optimisation problems searches.

Also the documentation says: "In addition, the users should not make use of these timers for their own purposes if they plan to use the after event mechanism." in last sentence of paragraph 14.1.2 which I do not understand.

I would like to set an after event that is associated with user cputime to avoid variations between runs: is that possible in Linux?

And although I am not quite there yet, if and when I do move to using Engine and Threads I am right to assume that every thread (engine?) will use its own 'real' time (assuming cpu time is not available)?

Thanks for the support.
Chris

--
Dr Chris Meudec<http://www.echancrure.eu/> (he/him) Maitrise, PhD, MA (T&L)
Lecturer in Software Development
South East Technological University - Carlow Campus - Ireland
E chr...@se...<mailto:chr...@se...> |  setu.ie<https://setu.ie/>
[turn on images]<https://setu.ie/>

Kilkenny Road Campus, Kilkenny Road, Carlow, R93 V960, Ireland
Campas Bhóthar Chill Chainnigh, Bóthar Chill Chainnigh, Ceatharlach, R93 V960, Éire

[eclipse-clp-users] Logtalk 3.83.0 released [CORRECTED]

[Paulo M. <pm...@lo...>]

Hi,

Logtalk 3.83.0 is now available for downloading at:

https://logtalk.org/

This release adds a new consistency_error/3 built-in method; makes the compiler consistency errors more informative; provides linter fixes and improvements; fixes some compiler bugs, notably using a uses/2 directive to change the order of predicate arguments to use it as a closure; improves the Handbook documentation of the info/2 and mode/2 directives; improves the Handbook documentation of the error handling built-in methods; improves the Handbook section on lambda expressions; updates the lgtunit, help, and tutor tools; adds additional tests for the Prolog standard logical update semantics and for several Prolog standard predicates; improves tests for Prolog standard control constructs and predicates; updates tests for linter flags; includes fixes for the SWI-Prolog based Docker image; and provides portability updates for XVM.

For details and a complete list of changes, please consult the release notes at:

https://github.com/LogtalkDotOrg/logtalk3/blob/master/RELEASE_NOTES.md

You can show your support for Logtalk continued development and success at GitHub by giving us a star and a symbolic sponsorship:

https://github.com/LogtalkDotOrg/logtalk3

Happy logtalking!
Paulo

-----------------------------------------------------------------
Paulo Moura
Logtalk developer

[eclipse-clp-users] Logtalk 3.83.0 released

[Paulo M. <pm...@lo...>]

Hi,

Logtalk 3.82.0 is now available for downloading at:

https://logtalk.org/

This release adds support for runtime constructed messages for the built-in methods; fixes error handling for the include/1 directive when dynamically creating new entities; includes changes, improvements, fixes, and tests for the linter tool; improves Handbook documentation of the message printing mechanism predicates; improves the packs tool handling of alternative pack dependencies; improves support for pack virtual environments; improves support for Allure test reports; includes additional tests for standard directives and predicates; and provides improvements and fixes for the portable Docker image. Thanks to Alex Kouznetsov and Paul Brown for the bug reports.

For details and a complete list of changes, please consult the release notes at:

https://github.com/LogtalkDotOrg/logtalk3/blob/master/RELEASE_NOTES.md

You can show your support for Logtalk continued development and success at GitHub by
giving us a star and a symbolic sponsorship:

https://github.com/LogtalkDotOrg/logtalk3

Happy logtalking!
Paulo

-----------------------------------------------------------------
Paulo Moura
Logtalk developer

[eclipse-clp-users] Logtalk 3.82.0 released

[Paulo M. <pm...@lo...>]

Hi,

Logtalk 3.82.0 is now available for downloading at:

https://logtalk.org/

This release adds support for runtime constructed messages for the built-in methods; fixes error handling for the include/1 directive when dynamically creating new entities; includes changes, improvements, fixes, and tests for the linter tool; improves Handbook documentation of the message printing mechanism predicates; improves the packs tool handling of alternative pack dependencies; improves support for pack virtual environments; improves support for Allure test reports; includes additional tests for standard directives and predicates; and provides improvements and fixes for the portable Docker image. Thanks to Alex Kouznetsov and Paul Brown for the bug reports.

For details and a complete list of changes, please consult the release notes at:

https://github.com/LogtalkDotOrg/logtalk3/blob/master/RELEASE_NOTES.md

You can show your support for Logtalk continued development and success at GitHub by
giving us a star and a symbolic sponsorship:

https://github.com/LogtalkDotOrg/logtalk3

Happy logtalking!
Paulo

-----------------------------------------------------------------
Paulo Moura
Logtalk developer

Re: [eclipse-clp-users] Attributed variables unification failure within a conditional construct

[Joachim S. <jsc...@co...>]

On 30/07/2024 15:24, Chris Meudec wrote:
> Hi all,
> I am getting reacquainted with ECLiPSe Prolog after some time with Sicstus, so 
> it appears I am rusty.
> 
> I have used attributed variables extensively in the past, but I am stuck.
> I have defined an attributed variable and have defined a unification handler, 
> but whenever my unification handler fails (as it should)  as part of a condition 
> in a condition construct (*+Condition -> +Then ; +Else*) the entire construct 
> fails rather than executing the Else part.
> 
> I have condensed the problem to a short example below.
> 
> :- module('try').
> :- meta_attribute('try', [unify:unify_name/2]).
> 
> unify_name(_, Attr) :-
>      var(Attr).
> unify_name(Term, Attr) :-
>      compound(Attr),
>      unify_term_name(Term, Attr).
> 
> unify_term_name(_{AttrY}, AttrX) :-
>      -?->
>      AttrX = AttrY.
> 
> try :-
>      add_attribute(X, try('X')),
>      Declarator = X,
>      (Declarator = 2 ->        %when unification fails here as it should, the 
> else part is not executed as expected
>          printf("hello there 10", [])
>      ;
>          printf("hello there 20", [])
>      ).
> try :-
> printf("hello there 30", []).
> 
> I get 30 printed out but I was expecting 20.
> 
> Why? It is rather odd.
> 
> With this attribute, I only want it to succeed when unified with a free variable.
> 
> I could avoid using the conditional construct in such cases but it does not help 
> my understanding and the current behaviour is a little surprising to me.
> 
> Thanks,
> Chris


Hi Chris,

Short answer: as a workaround, insert true/0 after the unification(s) that you 
expect to trigger the failure:

try :-
     add_attribute(X, try('X')),
     Declarator = X,
     (Declarator = 2, true ->          % true/0 forces handlers & waking
         printf("hello there 10", [])
     ;
         printf("hello there 20", [])
     ).



Background: when attributed variables are involved in unifications, the system 
invokes the associated unify-handler(s).  While in principle this should happen 
just after unification, for technical reasons handlers only execute when control 
flow reaches the next "trigger point".  This is typically after a sequence of 
simple goals (such as =/2, simple arithmetic, etc), but before the next regular 
subgoal, e.g.

    ..., X=1, Y=2, Z=3, /*HANDLE X,Y,Z HERE*/ q(...), ...

Unfortunately, owing to a historic design decision for efficiency reasons, cuts 
and -> are classified as simple subgoals.  This means that handlers may 
counter-intuitively slip over and execute _after_ a cut (or a commit to a 
conditional branch as in your example).

As shown above, a dummy subgoal (such as true/0) can always be used to instruct 
the compiler to insert a handler trigger point at an earlier position.

Regards,
Joachim

[eclipse-clp-users] Attributed variables unification failure within a conditional construct

[Chris M. <Chr...@se...>]

Hi all,
I am getting reacquainted with ECLiPSe Prolog after some time with Sicstus, so it appears I am rusty.

I have used attributed variables extensively in the past, but I am stuck.
I have defined an attributed variable and have defined a unification handler, but whenever my unification handler fails (as it should)  as part of a condition in a condition construct (+Condition -> +Then ; +Else) the entire construct fails rather than executing the Else part.

I have condensed the problem to a short example below.

:- module('try').
:- meta_attribute('try', [unify:unify_name/2]).

unify_name(_, Attr) :-
    var(Attr).
unify_name(Term, Attr) :-
    compound(Attr),
    unify_term_name(Term, Attr).

unify_term_name(_{AttrY}, AttrX) :-
    -?->
    AttrX = AttrY.

try :-
    add_attribute(X, try('X')),
    Declarator = X,
    (Declarator = 2 ->        %when unification fails here as it should, the else part is not executed as expected
        printf("hello there 10", [])
    ;
        printf("hello there 20", [])
    ).
try :-
printf("hello there 30", []).

I get 30 printed out but I was expecting 20.

Why? It is rather odd.

With this attribute, I only want it to succeed when unified with a free variable.

I could avoid using the conditional construct in such cases but it does not help my understanding and the current behaviour is a little surprising to me.

Thanks,
Chris
--
Dr Chris Meudec<http://www.echancrure.eu/> (he/him) Maitrise, PhD, MA (T&L)
Lecturer in Software Development
South East Technological University - Carlow Campus - Ireland
E chr...@se...<mailto:chr...@se...> |  setu.ie<https://setu.ie/>
[turn on images]<https://setu.ie/>

Kilkenny Road Campus, Kilkenny Road, Carlow, R93 V960, Ireland
Campas Bhóthar Chill Chainnigh, Bóthar Chill Chainnigh, Ceatharlach, R93 V960, Éire

[eclipse-clp-users] Logtalk 3.81.0, Logtalk for VSCode 0.23.0, and Docker image releases

[Paulo M. <pm...@lo...>]

Hi,

Logtalk 3.81.0 is now available for downloading at:

https://logtalk.org/

This release updates the delegation control construct to also preserve the original meta-call context; adds support for runtime constructed "(^^)/2" goals; adds support for using the "(<<)/2" and "catch/3" control constructs in a grammar rule body; fixes meta-arguments handling issues (thanks to Alex Kouznetsov for the bug reports); accounts for the renaming of the LVM backend to XVM; improves documentation; improves the performance of the "json" library when parsing large files (thanks to Yurii Rashkovskii for the bug report); fixes the "meta_compiler" library expansion of meta-arguments that call Prolog module predicates; changes the "lgtunit" object "test/3" private predicate to no longer being declared as a meta-predicate, simplifying writing of meta-predicate tests; adds support for conditional and triggered breakpoints to the "debugger" tool; improves the "debugger" tool support for log points; improves the "debugger" tool performance when checking for leashed ports; fixes a bug in the "lgtdoc" tool when generating reStructuredText files; adds a new programming example illustrating the semantics of calling an inherited meta-predicate using a message to "self" versus using a "super" call; includes additional tests for the "(^^)/2" control construct; adds a Docker file for building an image with Logtalk, a subset of the supported Prolog backends, Jupyter, JupyterLab, and the Logtalk kernel; and includes new and improved VSCode/VSCodium support.

For details and a complete list of changes, please consult the release notes at:

https://github.com/LogtalkDotOrg/logtalk3/blob/master/RELEASE_NOTES.md


Logtalk for VSCode 0.23.0 is now available from both VSCode and VSCodium marketplaces:

https://marketplace.visualstudio.com/items?itemName=LogtalkDotOrg.logtalk-for-vscode

https://open-vsx.org/extension/LogtalkDotOrg/logtalk-for-vscode

This is a major release, providing improved usability, improved debugging support, new commands, and bug fixes:

* Rename workspace commands to include instead the word "Project"
* Show only project (workspace) commands in the explorer context menu
* Change the "Logtalk: Make ..." commands to show a warning when no Logtalk process is running
* Add "Logtalk: Create Project" command
* Add "Logtalk: Load Project" command
* Add getting started walkthrough
* Add failed tests to the "Problems" pane (when using the "Logtalk: Run Tests" command)
* Add support for conditional and triggered breakpoints
* Escape log point messages to ensure they are valid quoted atoms
* More informative error message when a script is not found
* Fix workspace commands when run from the command palette by using the first workspace folder
* Fix the "Logtalk: Load Directory" command to show a warning if the loader file doesn't exist
* Fix the "Logtalk: Run Tests" command to show a warning if the tester file doesn't exist
* Fix the "Logtalk: Run Doclet" command to show a warning if the doclet file doesn't exist

https://github.com/LogtalkDotOrg/logtalk-for-vscode/releases/tag/v0.23.0


Docker image with Logtalk, Prolog systems, and Jupyter available:

https://hub.docker.com/r/logtalk/logtalk3-portable/tags

Includes:

* Logtalk 3.81.0
* B-Prolog 8.1
* Ciao Prolog 1.23.0-m1
* CxProlog 0.98.3
* ECLiPSe 7.1#13
* GNU Prolog latest git master version
* SWI-Prolog latest git master version
* Trealla Prolog latest git main version
* XSB latest git git-origin version 
* YAP latest git master version
* Dependencies for the Logtalk developer tools
* Latest Jupyter version


You can show your support for Logtalk continued development and success at GitHub by giving us a star and a symbolic sponsorship:

https://github.com/LogtalkDotOrg/logtalk3

Happy logtalking!
Paulo

-----------------------------------------------------------------
Paulo Moura
Logtalk developer

[eclipse-clp-users] Logtalk 3.80.0 and Logtalk for VSCode 0.22.0 released

[Paulo M. <pm...@lo...>]

Hi,

Logtalk 3.80.0 is now available for downloading at:

https://logtalk.org/

This release changes the debugging API to allow multiple debug handlers to be loaded simultaneously; updates the compiler to support for using backend proprietary directives when dynamically creating objects and categories; updates the reflection API to better support developer tools; fixes a regression preventing linter warnings for duplicated clauses and grammar rules; fixes reporting of the number of compilation warnings that failed to count some of the warnings; fixes the `phrase/2-3` built-in methods to properly handle a runtime bound first argument when called from a meta-predicate (thanks to Alex Kouznetsov for the bug report); updates the documentation of the embedding scripts; adds ew `sequential_occurrences/2-3` list predicates to the `types` library; updates the he `debugger` and `ports_profiler` tools for the new debug API; adds support for log points to the `debugger` tool; improves the `debugger` tool integration with other developer tools; improves the `packs` tool reporting when a pack is available from multiple registries; includes fixes for the `missing_data` example; includes new and improved VSCode/VSCodium support predicates; and provides portability updates for LVM and SWI-Prolog.

For details and a complete list of changes, please consult the release notes at:

https://github.com/LogtalkDotOrg/logtalk3/blob/master/RELEASE_NOTES.md


Logtalk for VSCode 0.22.0 is now available from both VSCode and VSCodium marketplaces:

https://marketplace.visualstudio.com/items?itemName=LogtalkDotOrg.logtalk-for-vscode

https://open-vsx.org/extension/LogtalkDotOrg/logtalk-for-vscode

This is a major release, providing improved usability, initial debugging support, new commands, and bug fixes:

* Change linters to no longer create and write to an "OUTPUT" pane channel
* Show current clause in the active text editor when debugging
* Add support for adding and removing spy points and log points
* Add Logtalk source file icons
* Add "Logtalk: Make - Circular" command
* Add "Logtalk: Make - Optimal" command
* Add "Logtalk: Make - Normal" command
* Add "Logtalk: Make - Debug" command
* Add "Logtalk: Make - Clean" command
* Add "Logtalk: Make - Caches" command
* Improve usability by only showing the terminal if hidden when advisable by the command
* Update minimum VSCode version required to 1.64.0
* Update the "Go to Implementations" command to also find protocol implementations
* Fix file recompilation to clear previous diagnostics for the file
* Fix possible JavaScript error in the "Go to Symbol in Editor..." implementation
* Fix occasional glitch where code navigation would return a previous result
* Fix and simplify auto-indentation patterns
* Fix parsing of predicate calls with double-quoted arguments

https://github.com/LogtalkDotOrg/logtalk-for-vscode/releases/tag/v0.22.0

You can show your support for Logtalk continued development and success at GitHub by giving us a star and a symbolic sponsorship:

https://github.com/LogtalkDotOrg/logtalk3

Happy logtalking!
Paulo

[eclipse-clp-users] Logtalk 3.79.0 and Logtalk for VSCode 0.21.0 released

[Paulo M. <pm...@lo...>]

Hi,

Logtalk 3.79.0 is now available for downloading at:

https://logtalk.org/

This release fixes a regression in the "make" tool for the "check" target; fixes the term-expansion mechanism to allow generating multiple entity definitions; fixes left-recursion linter warnings for coinductive predicates; fixes the "code_metrics" tool implementation of the cyclomatic complexity and unique predicate nodes metrics to take into account multifile predicate definitions; fixes the "wrapper" tool reporting of missing meta_predicate/1 directives; changes the "dead_code_scanner" and "lgtdoc" tools to print warnings using the same format used by the compiler; provides Handbook improvements; and includes new and improved VSCode/VSCodium support predicates. Thanks to Alex Kouznetsov for his bug reports and documentation feedback.

For details and a complete list of changes, please consult the release notes at:

https://github.com/LogtalkDotOrg/logtalk3/blob/master/RELEASE_NOTES.md


Logtalk for VSCode 0.21.0 is also now available from both VSCode and VSCodium marketplaces:

https://marketplace.visualstudio.com/items?itemName=LogtalkDotOrg.logtalk-for-vscode

https://open-vsx.org/extension/LogtalkDotOrg/logtalk-for-vscode

This is a major release, providing better integration with developer tools, new commands, improved usability, and bug fixes:

- Changed commands that run the developer tools to require the code to be loaded first
- The user is now warned when no code is loaded for a command that requires it
- The user is now informed when commands that spawn processes complete
- Added experimental code lens support for test results
- Added experimental code lens support for entity cyclomatic complexity
- Added "Logtalk: Compute Metrics" command
- Added "Logtalk: Toggle Code Lens" command
- Added "Logtalk: Generate Documentation (workspace)" command
- Added "Logtalk: Generate Diagrams (workspace)" command
- Added "Logtalk: Scan Dead Code (workspace)" command
- Added "dead_code_scanner" tool warnings to the "Problems" pane
- Added "lgtdoc" tool warnings to the "Problems" pane
- Added "make" tool warnings to the "Problems" pane
- Added tests compilation warnings and errors to the "Problems" pane
- Added doclet compilation warnings and errors to the "Problems" pane
- Updated the "Known Issues" section in the readme file
- Fixed taking into account environment settings when spawning auxiliary Logtalk processes
- Fixed off-by-one error when parsing linter warnings lines
- Fixed deleting an atom or variable when typing an underscore before the first character

https://github.com/LogtalkDotOrg/logtalk-for-vscode/releases/tag/v0.21.0

The previous release implemented code navigation features:

- Go to Declaration
- Go to Definition
- Go to Type Definition
- Go to References
- Go to Implementations
- Go to Symbol in Editor...
- Go to Symbol in Workspace...
- Show Call Hierarchy
- Show Type Hierarchy

You can show your support for Logtalk continued development and success at GitHub by giving us a star and a symbolic
sponsorship:

https://github.com/LogtalkDotOrg/logtalk3

Happy logtalking!
Paulo



-----------------------------------------------------------------
Paulo Moura
Logtalk developer

[eclipse-clp-users] Logtalk 3.78.0 and Logtalk for VScode 0.20.0 released

[Paulo M. <pm...@lo...>]

Hi,

Logtalk 3.78.0 is now available for downloading at:

https://logtalk.org/

This release improves the reflection API for better support code navigation features in IDEs and text editors; adds a new linter warning for left-recursion on clauses and grammar rules; includes documentation updates; fixes a portability issue in the `dead_code_scanner` tool; includes additional tests for Prolog standard predicates; adds support for VSCode and VSCodium code navigation features; and provides portability updates for SICStus Prolog and SWI-Prolog.

For details and a complete list of changes, please consult the release notes at:

https://github.com/LogtalkDotOrg/logtalk3/blob/master/RELEASE_NOTES.md


Logtalk for VSCode 0.20.0 is also now available from both VSCode and VSCodium marketplaces:

https://marketplace.visualstudio.com/items?itemName=LogtalkDotOrg.logtalk-for-vscode

https://open-vsx.org/extension/LogtalkDotOrg/logtalk-for-vscode

This is a major release, implementing code navigation features (requires Logtalk 3.78.0 or later version):

- Go to Declaration
- Go to Definition
- Go to Type Definition
- Go to References
- Go to Implementations
- Go to Symbol in Editor...
- Go to Symbol in Workspace...

There's also a new "Open Parent File" command. For details and a complete list of changes, please consult the release notes at:

https://github.com/LogtalkDotOrg/logtalk-for-vscode/releases/tag/v0.20.0


You can show your support for Logtalk continued development and success at GitHub by giving us a star and a symbolic
sponsorship:

https://github.com/LogtalkDotOrg/logtalk3

Happy logtalking!
Paulo


-----------------------------------------------------------------
Paulo Moura
Logtalk developer

[eclipse-clp-users] Logtalk 3.74.0 released

[Paulo M. <pm...@lo...>]

Hi,

Logtalk 3.74.0 is now available for downloading at:

https://logtalk.org/

This release improves the linter warnings for unsound constructs in grammar rules and for if-then-else and soft-cut control constructs; improves the semantics and implementation of several multi-threading features; fixes compilation of "phrase/2-3" goals where the first argument is a "(::)/1-2" or "(^^)/2" control construct with a variable grammar rule body argument; fixes a regression where a compiler error when a source file term is not callable would be delegated to the backend; improves the Handbook documentation of several directives and built-in predicates; improves the Handbook documentation on dynamic predicates and grammar rules; adds a "listing" library (replacing the old undocumented one); adds a "recorded_database" library to help porting legacy Prolog code; fixes "json" library bugs; updates the "help" tool support to browse the Handbook and APIs documentation from the top-level; changes the default output directory for the "diagrams" tool to "./dot_dias"; updates the "tutor" tool for all recent linter updates; fixes a syntax error in the "logtalk_tester.ps1" script; improves the portability of the "fcube" port; updates the Advent of Code 2023 examples and several of the multi-threading examples; adds additional tests for the de facto standard "format/2-3" predicates and for the multi-threading built-in predicates; updates support for several text editors and syntax highlighters; updates the manual installation script to inform the user about the "INFOPATH" environment variable; fixes the Bash shell embedding scripts to actually use the default settings file when no "-s" option is passed; and includes portability updates for CxProlog, LVM, SICStus Prolog, SWI-Prolog, XSB, and YAP. Thanks to Yurii Rashkovskii for his bug reports and suggestions.

For details and a complete list of changes, please consult the release notes at:

https://github.com/LogtalkDotOrg/logtalk3/blob/master/RELEASE_NOTES.md

You can show your support for Logtalk continued development and success at GitHub by giving us a star and a symbolic sponsorship:

https://github.com/LogtalkDotOrg/logtalk3

Happy logtalking!
Paulo

-----------------------------------------------------------------
Paulo Moura
Logtalk developer

[eclipse-clp-users] Logtalk 3.73.0 released

[Paulo M. <pm...@lo...>]

Hi,

Logtalk 3.73.0 is now available for downloading at:

https://logtalk.org/

This release adds linter warnings for deprecated arithmetic predicates and functions; adds warnings for comparing numbers using unification; adds support for using backend-declared deprecated built-in predicates in linter warnings; improves checking the availability of predicates in "user" for "uses/2" and "use_module/2" directives; avoids false positive linter warnings about non-terminals called as predicates when the caller is a phrase-like predicate declared in the backend adapter file; improves compiler reporting of term-expansion errors; fixes unknown and undefined predicate call warnings when the calls occur in an included file to report the actual location instead of the main file; fixes printing of grammar rules linter warnings to respect the "grammar_rules" flag; adds adapter files support for deprecated built-in predicates and for declaring phrase-like predicates that call non-terminals; improves the Handbook grammar section now uses W3C-style EBNF syntax compatible with the [Railroad Diagram Generator](https://www.bottlecaps.de/rr/ui), also fixing typos and omissions; improves the Handbook section on parametric objects; improves the documentation of the "wrapper" tool; adds an experimental "mutations" library for generating random mutations of terms of selected types (intended for eventual fuzz testing support); adds a "tsv" library for reading and writing TSV files; adds new predicates and non-terminals to the "types", "grammars", and "random" libraries; improves the performance of the "term_io" library predicates; includes updates and fixes to the "lgtunit", "tutor", and "wrapper" tools; fixes the PowerShell documentation scripts to avoid an error when converting XML files; improves the "logtalk_tester" scripts detection and reporting of broken test sets due to backend bugs; adds new "haunted_wasteland", "scratchcards", and "trebuchet" examples (solving Advent of Code 2023 problems); adds new tests, updates, and fixes issues with the "poem", "profiling", "self_vs_this", "errors", "bench", and "benchmarks" examples; adds additional tests for the "phrase/2-3" built-in methods and fixes an issue with a "setof/3" built-in method test; improves the macOS installer; fixes the "logtalk_user_setup.ps1" PowerShell script to use a valid path for the backup directory; and includes portability updates for B-Prolog, CxProlog, ECLiPSe, LVM, and SWI-Prolog. Thanks to Domingo Alvarez Duarte and Yurii Rashkovskii for their contributions to this release.

For details and a complete list of changes, please consult the release notes at:

https://github.com/LogtalkDotOrg/logtalk3/blob/master/RELEASE_NOTES.md

You can show your support for Logtalk continued development and success at GitHub by giving us a star and a symbolic sponsorship:

https://github.com/LogtalkDotOrg/logtalk3

Happy logtalking!
Paulo

-----------------------------------------------------------------
Paulo Moura
Logtalk developer

Re: [eclipse-clp-users] cannot run tkeclipse on Windows 10

[koyahata <koy...@ko...>]

Dear Joachim,

Thank you for the detailed answer and I apologize for late reply.

I can run DosEclipse with no problem.

I checked HKEY_LOCAL_MACHINE\SOFTWARE\IC-Parc\Eclipse\7.1\ECLIPSEDIR is 
pointing to "C:\Program Files\ECLiPSe 7.1"

I found all files you listed in C:\Program Files\ECLiPSe 7.1\lib\x86_64_nt

I added new windows account and could run tkeclipse successfully with 
this account.
So this problem seems to come from windows account properties.
I added and removed administrator authority into this account and
tkeclipse could be run from both.


On 2023/08/05 21:49, Joachim Schimpf via ECLiPSe-CLP-Users wrote:
> Dear Taku Koyahata,
> 
> I have just tried a fresh installation on a Windows 10 Home version 22H2 
> (not Japanese version though) and cannot reproduce the problem.  Windows 
> 11 also works fine.
> 
> Can you start DosEclipse successfully?
> 
> In your registry, you should have an entry 
> HKEY_LOCAL_MACHINE\SOFTWARE\IC-Parc\Eclipse\7.1\ECLIPSEDIR pointing to 
> "C:\Program Files\ECLiPSe 7.1"
> 
> and the following DLLs as a result of installing ECLiPSe:
> 
> Directory of C:\Program Files\ECLiPSe 7.1\lib\x86_64_nt
> 
> 24/05/2023  14:14    <DIR>          .
> 24/05/2023  14:14    <DIR>          ..
> 01/01/2023  19:07           319,482 bitmap.dll
> 01/01/2023  19:07           331,906 dbi_mysql.dll
> 01/01/2023  19:06            25,089 eclipse.def
> 01/01/2023  19:06         1,411,204 eclipse.dll
> 01/01/2023  19:06            96,514 eclipse.dll.a
> 01/01/2023  19:06            22,528 eclipse.exe
> 01/01/2023  19:07           306,688 ec_java.dll
> 01/01/2023  19:07           299,465 ec_java_load.dll
> 01/01/2023  19:07           310,236 edge_finder.dll
> 01/01/2023  19:07           360,145 eregex.dll
> 01/01/2023  19:07        10,295,296 gfd.dll
> 01/01/2023  19:07           355,650 ic.dll
> 01/01/2023  19:05             2,261 INST_PARAMS
> 01/01/2023  19:05         1,073,455 libgmp-10.dll
> 01/01/2023  19:05             4,096 Makefile.external
> 01/01/2023  19:06         6,021,120 seosiclpcbc.dll
> 01/01/2023  19:06           316,015 tkeclipse.dll
> 01/01/2023  19:06               130 tkexdr.def
> 01/01/2023  19:06           312,016 tkexdr.dll
> 01/01/2023  19:06             2,006 tkexdr.dll.a
>                20 File(s)     21,865,302 bytes
> 
> The error message isn't very specific, it might be a permission problem 
> or your particular virus scanner causing trouble.
> 
> Regards,
> Joachim
> 
> 
> On 31/07/2023 09:01, koyahata wrote:
>> I downloaded ECLiPSe_7.1_13_x86_64_nt.exe from the path below
>> https://eclipseclp.org/Distribution/Builds/7.1_13/x86_64_nt/ .
>> After downloading and installing ECLiPSe, running tkeclipse cause the 
>> caution below:
>>
>> ------------
>> couldn't initialize ECLiPSe while executing "ec_init_"
>> (procedure "ec_init" line 7)
>> invoked from within
>> "ec_init"
>> (file "C:\Program Files\ECLiPSe 7.1\lib_tcl\tkeclipse.tcl" line 1124.
>> -------------
>>
>> After this caution occurs, It cannot continue anymore.
>> I'm using Windows 10 Home version 22H2.
>>
>> Does anyone have any suggestions to fix this problem?
>> Any help will be appreciated.
>>
>> Regards,
>> Taku Koyahata
>>
>>
>> _______________________________________________
>> ECLiPSe-CLP-Users mailing list
>> ECL...@li...
>> https://lists.sourceforge.net/lists/listinfo/eclipse-clp-users
> 
> 
> 
> _______________________________________________
> ECLiPSe-CLP-Users mailing list
> ECL...@li...
> https://lists.sourceforge.net/lists/listinfo/eclipse-clp-users

Re: [eclipse-clp-users] cannot run tkeclipse on Windows 10

[Joachim S. <jsc...@co...>]

Dear Taku Koyahata,

I have just tried a fresh installation on a Windows 10 Home version 22H2 (not Japanese version 
though) and cannot reproduce the problem.  Windows 11 also works fine.

Can you start DosEclipse successfully?

In your registry, you should have an entry 
HKEY_LOCAL_MACHINE\SOFTWARE\IC-Parc\Eclipse\7.1\ECLIPSEDIR pointing to "C:\Program Files\ECLiPSe 7.1"

and the following DLLs as a result of installing ECLiPSe:

Directory of C:\Program Files\ECLiPSe 7.1\lib\x86_64_nt

24/05/2023  14:14    <DIR>          .
24/05/2023  14:14    <DIR>          ..
01/01/2023  19:07           319,482 bitmap.dll
01/01/2023  19:07           331,906 dbi_mysql.dll
01/01/2023  19:06            25,089 eclipse.def
01/01/2023  19:06         1,411,204 eclipse.dll
01/01/2023  19:06            96,514 eclipse.dll.a
01/01/2023  19:06            22,528 eclipse.exe
01/01/2023  19:07           306,688 ec_java.dll
01/01/2023  19:07           299,465 ec_java_load.dll
01/01/2023  19:07           310,236 edge_finder.dll
01/01/2023  19:07           360,145 eregex.dll
01/01/2023  19:07        10,295,296 gfd.dll
01/01/2023  19:07           355,650 ic.dll
01/01/2023  19:05             2,261 INST_PARAMS
01/01/2023  19:05         1,073,455 libgmp-10.dll
01/01/2023  19:05             4,096 Makefile.external
01/01/2023  19:06         6,021,120 seosiclpcbc.dll
01/01/2023  19:06           316,015 tkeclipse.dll
01/01/2023  19:06               130 tkexdr.def
01/01/2023  19:06           312,016 tkexdr.dll
01/01/2023  19:06             2,006 tkexdr.dll.a
               20 File(s)     21,865,302 bytes

The error message isn't very specific, it might be a permission problem or your particular virus 
scanner causing trouble.

Regards,
Joachim


On 31/07/2023 09:01, koyahata wrote:
> I downloaded ECLiPSe_7.1_13_x86_64_nt.exe from the path below
> https://eclipseclp.org/Distribution/Builds/7.1_13/x86_64_nt/ .
> After downloading and installing ECLiPSe, running tkeclipse cause the caution below:
> 
> ------------
> couldn't initialize ECLiPSe while executing "ec_init_"
> (procedure "ec_init" line 7)
> invoked from within
> "ec_init"
> (file "C:\Program Files\ECLiPSe 7.1\lib_tcl\tkeclipse.tcl" line 1124.
> -------------
> 
> After this caution occurs, It cannot continue anymore.
> I'm using Windows 10 Home version 22H2.
> 
> Does anyone have any suggestions to fix this problem?
> Any help will be appreciated.
> 
> Regards,
> Taku Koyahata
> 
> 
> _______________________________________________
> ECLiPSe-CLP-Users mailing list
> ECL...@li...
> https://lists.sourceforge.net/lists/listinfo/eclipse-clp-users

[eclipse-clp-users] cannot run tkeclipse on Windows 10

[koyahata <koy...@ko...>]

I downloaded ECLiPSe_7.1_13_x86_64_nt.exe from the path below
https://eclipseclp.org/Distribution/Builds/7.1_13/x86_64_nt/ .
After downloading and installing ECLiPSe, running tkeclipse cause the 
caution below:

------------
couldn't initialize ECLiPSe while executing "ec_init_"
(procedure "ec_init" line 7)
invoked from within
"ec_init"
(file "C:\Program Files\ECLiPSe 7.1\lib_tcl\tkeclipse.tcl" line 1124.
-------------

After this caution occurs, It cannot continue anymore.
I'm using Windows 10 Home version 22H2.

Does anyone have any suggestions to fix this problem?
Any help will be appreciated.

Regards,
Taku Koyahata

[eclipse-clp-users] Planning as Theorem Proving with Heuristics: arxiv.org/abs/2303.13638

[Mikhail S. <sou...@gm...>]

Greetings,

       If you are interested in modern heuristic Automated Planning, then
you will be pleased to learn that it can be done with PROLOG. I would like
to inform you about a recent deductive planner TPLH implemented in ECLiPSe
PROLOG. TPLH is described in the paper

              Planning as Theorem Proving with Heuristics
              Mikhail Soutchanski, Ryan Young
                            https://arxiv.org/abs/2303.13638
        Abstract
        Planning as a theorem proving in situation calculus was abandoned
50 years ago as an impossible project. But we have developed a Theorem
Proving Lifted Heuristic (TPLH) planner that searches for a plan in a tree
of situations using the A* search algorithm. It is  controlled by a delete
relaxation-based domain independent heuristic. We compare TPLH with the
state-of-the-art Fast Downward (FD) and Best First         Width Search
(BFWS) planners over several standard benchmarks. Since our implementation
of the heuristic function is not optimized, TPLH is slower than FD and
BFWS. But it computes shorter plans, and it explores fewer states. We
discuss previous research on planning within KRR and identify related
directions. Thus we show  that deductive lifted heuristic planning in
situation calculus is actually doable.

Comments are  welcome. I would be glad to collaborate on a related research
project.
Thanks,
============================================================
    Mikhail Soutchanski, Ph.D., Professor
    WWW:                   http://www.cs.torontomu.ca/mes
Department of Computer Science, #ENG275
Faculty of Science
Toronto Metropolitan (formerly Ryerson) University
245 Church Street
Toronto, Ontario,
M5B 2K3, Canada
============================================================