eclipse-clp-users — ECLiPSe Users List

[eclipse-clp-users] CLP/CBC Problem

[Thorsten W. <tho...@we...>]

Hi,

I found a strange bug with CLP/CBC and ECLiPSe 7.x (incl. 7.1.13). The 
program below returns a "no", as CLP/CBC seems to think that the problem 
is infeasible.
If a small change is made, e.g., B210 removed from the list of integers, 
then the solver returns the correct answer "0.0".
CPLEX or Xpress do not have a problem.
ECLiPSe 6.1 was also fine.

Cheers,
Thorsten




:- lib(eplex).

run(D) :-
         IntVars = [B11,B12,B13,B14,B15,B16,B17,B18,B19,B110,
                    B21,B22,B23,B24,B25,B26,B27,B28,B29,B210],
         100 $= C+sum(IntVars),
         R11 $= B11+B12+B13+B14+B15,
         R12 $= B16+B17+B18+B19+B110,
         R21 $= B21+B22+B23+B24+B25,
         R22 $= B26+B27+B28+B29+B210,
         R11 $>= 0,
         R11 $=< 30,
         R12 $>= 0,
         R12 $=< 30,
         R21 $>= 0,
         R21 $=< 20,
         R22 $>= 0,
         R22 $=< 20,
         C $>= 0,
         C $=< 100,
         eplex:integers(IntVars),
         eplex_solver_setup(min(C), D, [], []),
         eplex_solve(D).

[eclipse-clp-users] Logtalk 3.61.0 released

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

Hi,

Logtalk 3.61.0 is now available for downloading at:

https://logtalk.org/

This release provides updated for several Prolog backend adapters and integration scripts for use in the Jupyter kernel for Logtalk (https://github.com/LogtalkDotOrg/logtalk-jupyter-kernel); adds a new "ids" library for generating identifiers (Base64 encoded) with parametrizable text representation and number of bytes of randomness; adds new "pairs" library object predicates; adds "packs" tool support for using "git archive" for installing packs, providing a better user experience when the packs registry server uses Single Sign-On (SSO) for authentication; and includes additional tests for library predicates and standard arithmetic functions.

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] switching debugger on with trace

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

Hi Christophe,

After reading Kish's answer, and re-reading your question, I think you are in 
fact looking for the *breakpoint* facility. This allows you to stop the debugger 
at a particular line in the code. The documentation may be a bit brief on that.

The easiest way to set a breakpoint is with TkEclipse's tracer:

  * open the tracer
  * start executing your toplevel goal
  * the tracer will immediately stop at the first CALL
  * in the "Source Context" tab, navigate to the source location where you want
    to stop
  * to the left of the code you see a gutter with grey # symbols -- these are
    the locations where you can set a breakpoint
  * click on the # symbol to enable/disable a breakpoint (enabled ones are red)
  * click Leap to continue execution
  * the tracer will stop at the breakpoint

Tracer with breakpoint


Breakpoints can also be set via the command like, e.g.

?- spy "buggy.ecl":5.
breakpoint added to line 5 of file /homes/jschimpf/Playground/buggy.ecl in 
predicate eclipse : p / 0
Yes (0.00s cpu)


Hope that's what you needed,
-- Joachim


On 15/12/2022 23:44, Kish Shen wrote:
> Hi Chris,
>
> In ECLiPSe, I don't think you can turn on the debugger and trace the execution 
> starting from there.
> However, you can turn on the debugger for a specific goal by wrapping it with 
> trace/1 or debug.1. Using your example:
>
> big_goal1,
> trace(buggy_goal),
> big_goal2.
>
> If the debugger was off when you run the above query, then only buggy_goal 
> will be traced.
> The difference between trace/1 and debug/1 is that the debugger is in creep 
> mode for trace/1 and will  stop immediately, while debug/1 will only stop for 
> a predicate with a spy point.
>
> Running goals with the debugger on is much slower than without the debugger, 
> so using trace/1 and debug/1 avoids the overhead for goals you are not debugging.
> Is this the main reason why you want to trace the execution of buggy_goal?
>
> If instead you are  interested in  tracing a specific call to buggy_goal in 
> your source code, you can set a breakpoint on it in TkECLiPSe's debugger., so 
> that the debugger will stop only at the call port for that specific call.
>
> I am surprised that your mytrace/0 worked for you. As far as I can tell, 
> although mytrace/0 will turn on the debugger, the tracing will not start from 
> there, but only from your next top-level goal. You don't need to use spy/1 to 
> turn on the debugger - you can use the debugging flag for set_flag./2, but 
> this will also not start tracing immediately.
>
> --Kish
>
> On Thu, Dec 15, 2022 at 9:42 PM Chris Meudec <Chr...@se...> wrote:
>
>     I am reacquainting myself with ECLiPSe 7.0 after playing with SICSTUS for
>     a while...
>
>     I SICSTUS I can insert a call to the predicate 'trace' anywhere in my
>     code, and the debugger will awake and waits for my instructions there.
>
>     In ECLiPSe, trace seems to be a command, not a predicate, so I cannot do
>     the same.
>     spy/1 must be applied to a whole predicate so it cannot be used to switch
>     the debugger in between predicate calls. set_flag/3 also require a predicate
>
>     The best I can do to replicate that behaviour (after an hour of
>     experimentation!) is to create my own mytrace/0 predicate:
>
>     p:- big_goal1, mytrace, buggy_goal, big_goal2.
>
>     big_goal1.
>     buggy_goal.
>     big_goal2.
>
>     mytrace.
>     :- spy mytrace/0.
>
>     This works as expected: the debugger switches itself on and I can creep
>     through the rest of the code.
>     I could not get debug/1 on its own nor with set_flag/3 to work.
>
>
>     Is there a better way?
>
>     Thanks,
>     Chris
>     --
>     Dr Chris Meudec <http://www.echancrure.eu/>(he/him) Maitrise, PhD, MA (T&L)
>     Lecturer in Software Development
>     E 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 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] switching debugger on with trace

[Kish S. <kis...@gm...>]

Hi Chris,

In ECLiPSe, I don't think you can turn on the debugger and trace the
execution starting from there.
However, you can turn on the debugger for a specific goal by wrapping it
with trace/1 or debug.1. Using your example:

big_goal1,
trace(buggy_goal),
big_goal2.

If the debugger was off when you run the above query, then only buggy_goal
will be traced.
The difference between trace/1 and debug/1 is that the debugger is in creep
mode for trace/1 and will  stop immediately, while debug/1 will only stop
for a predicate with a spy point.

Running goals with the debugger on is much slower than without the
debugger, so using trace/1 and debug/1 avoids the overhead for goals you
are not debugging.
Is this the main reason why you want to trace the execution of buggy_goal?

If instead you are  interested in  tracing a specific call to buggy_goal in
your source code, you can set a breakpoint on it in TkECLiPSe's debugger.,
so that the debugger will stop only at the call port for that specific
call.

I am surprised that your mytrace/0 worked for you. As far as I can tell,
although mytrace/0 will turn on the debugger, the tracing will not start
from there, but only from your next top-level goal. You don't need to use
spy/1 to turn on the debugger - you can use the debugging flag for
set_flag./2, but this will also not start tracing immediately.

--Kish

On Thu, Dec 15, 2022 at 9:42 PM Chris Meudec <Chr...@se...> wrote:

> I am reacquainting myself with ECLiPSe 7.0 after playing with SICSTUS for
> a while...
>
> I SICSTUS I can insert a call to the predicate 'trace' anywhere in my
> code, and the debugger will awake and waits for my instructions there.
>
> In ECLiPSe, trace seems to be a command, not a predicate, so I cannot do
> the same.
> spy/1 must be applied to a whole predicate so it cannot be used to switch
> the debugger in between predicate calls. set_flag/3 also require a
> predicate
>
> The best I can do to replicate that behaviour (after an hour of
> experimentation!) is to create my own mytrace/0 predicate:
>
> p :- big_goal1, mytrace, buggy_goal, big_goal2.
>
> big_goal1.
> buggy_goal.
> big_goal2.
>
> mytrace.
> :- spy mytrace/0.
>
> This works as expected: the debugger switches itself on and I can creep
> through the rest of the code.
> I could not get debug/1 on its own nor with set_flag/3 to work.
>
>
> Is there a better way?
>
> Thanks,
> Chris
> --
> Dr Chris Meudec <http://www.echancrure.eu/> (he/him) Maitrise, PhD, MA
> (T&L)
> Lecturer in Software Development
> E chr...@se... |  *setu.ie* <https://setu.ie/>
> [image: 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 mailing list
> ECL...@li...
> https://lists.sourceforge.net/lists/listinfo/eclipse-clp-users
>

[eclipse-clp-users] switching debugger on with trace

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

I am reacquainting myself with ECLiPSe 7.0 after playing with SICSTUS for a while...

I SICSTUS I can insert a call to the predicate 'trace' anywhere in my code, and the debugger will awake and waits for my instructions there.

In ECLiPSe, trace seems to be a command, not a predicate, so I cannot do the same.
spy/1 must be applied to a whole predicate so it cannot be used to switch the debugger in between predicate calls. set_flag/3 also require a predicate

The best I can do to replicate that behaviour (after an hour of experimentation!) is to create my own mytrace/0 predicate:

p :- big_goal1, mytrace, buggy_goal, big_goal2.

big_goal1.
buggy_goal.
big_goal2.

mytrace.
:- spy mytrace/0.

This works as expected: the debugger switches itself on and I can creep through the rest of the code.
I could not get debug/1 on its own nor with set_flag/3 to work.


Is there a better way?

Thanks,
Chris
--
Dr Chris Meudec<http://www.echancrure.eu/> (he/him) Maitrise, PhD, MA (T&L)
Lecturer in Software Development
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] IC limitations

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

[using ECLiPSe 7.0]
I have a query about IC floats limitations.

I understand some of the limitations of interval arithmetic and that not all decimals can be represented accurately by floats.
But practically, I need to know what is the largest float range that can be used without generating aberrant results.

?- lib(ic).
Yes (0.08s cpu)
?- R $:: -5 .. 5, R $= 1.6.
R = 1.6__1.6000000000000005                           % That's ok
Yes (0.00s cpu)

?- R $:: -3.4028235 * 10 ^ 38 .. 3.4028235 * 10 ^ 38, R $= 1.6.    % i.e. single precision 32 bits C float range
R = 0.0__3.7778931862957162e+22                       % aberrant
Yes (0.00s CPU)

?- R $:: -3.4028235 * 10 ^ 3 .. 3.4028235 * 10 ^ 3, R $= 1.6.
R = 1.5999999999999091__1.6000000000003638            % I can live with that
Yes (0.00s cpu)

?- R $= 1.6.
R = 1.6__1.6                                          % but that would be nicer all the time
Yes (0.00s cpu)

?- R $:: -2 ^ 31 - 1 .. 2 ^ 31 - 1, R $= 1.6.                     % using the C long range: -2147483647 .. 2147483647
R = 1.5999999046325684__1.6000003814697266            % that's ok
Yes (0.00s cpu)

?- R $:: -3.4028235 * 10 ^ 20 .. 3.4028235 * 10 ^ 20, R $= 1.6.
R = 0.0__65536.0                                      % starting to be silly...
Yes (0.00s cpu)

It's the unpredictability that I have difficulties with.

What's the best way to deal with this? Not imposing bounds? Using a safe range, but which one?

Many thanks for your efforts

Regards,
Chris
--
Dr Chris Meudec<http://www.echancrure.eu/> (he/him) Maitrise, PhD, MA (T&L)
Lecturer in Software Development
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.60.0 released

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

Hi,

Logtalk 3.60.0 is now available for downloading at:

https://logtalk.org/

This release adds a new linter check for the availability of predicates (and non-terminals) listed in `uses/2` and `use_module/2` directives; improves the readability of default flag values printed at startup; updates all backend adapter files to recognize `.pro` as a valid Prolog file name extension; includes Handbook, library, and tools documentation improvements; updates the manual installation instructions for `zsh` users; adds `json` library support for customizing the term representation of JSON objects and JSON pairs; adds new `reader::line_to_chars/2-3` library predicates; adds new and improved linter checks to the `lgtdoc` tool; adds a new `lgtunit` tool `file_path/2` predicate; includes fixes for the `logtalk_doclet` and `logtalk_tester` scripts; includes additional tests for several Prolog standard predicates; updated the `logtalk_user_setup` scripts to prevent misuse; and adds support for escape sequences inside double-quoted terms to most text editors and syntax highlighters.

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.59.0 released

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

Hi,

Logtalk 3.59.0 is now available for downloading at:

https://logtalk.org/

This release adds a new linter warning for naked meta-variables; adds linter warnings to the "lgtdoc" tool; updates the Bash shell integration scripts to be aware of the default Homebrew installation directory on macOS; updates all PowerShell scripts to check for a compatible PowerShell version; improves several Handbook sections; improves the documentation of the "random" and "types" libraries; includes fixes for the "logtalk_tester.ps1" script; updates the "lgtunit" tool to print a warning on invalid test options; fixes "lgtdoc" issues; updates and adds new Prolog standards compliance tests; adds new library predicates; and includes portability updates for Ciao Prolog and SICStus 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

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.58.0 released

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

Hi,

Logtalk 3.58.0 is now available for downloading at:

https://logtalk.org/

This release adds a new linter warning for non-terminals called as predicates; adds a compilation warning when compiling a "logtalk_load_context/2" goal with an invalid key; fixes the compiler to not throw an instantiation error when the body of a clause is a variable; improves documentation on third-party dependencies to build documentation final formats and to use the developer tools; improves Handbook, libraries, and tools documentation; provides fixes and improvements for the "os", "types", and "arbitrary" libraries; includes a new "lgtunit" version with improved QuickCheck support; adds experimental predicates to the "help" tool to browse and search inline at the top-level the Texinfo versions of the Handbook and APIs documentation; fixes a missing message tokenization in the "packs" tool; adds new Net-Clause Language (NCL) examples; adds new compliance tests for standard Prolog predicates and operators; adds a port of FCube, a prover for intuitionistic propositional logic; adds Emacs code snippets, contributed by Paul Brown; provides an embedding script for Ciao Prolog and improves the documentation of the embedding scripts; provides a PowerShell script for building the Handbook; updates the release build script to include all final formats for the Handbook and APIs documentation in the generated archives and installers; and includes portability updates for LVM, Trealla Prolog, and YAP.

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.57.0 released

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

Hi,

Logtalk 3.57.0 is now available for downloading at:

https://logtalk.org/

This release improves the linter tool with new and refined warnings; improves the compilation of Prolog modules as objects; refines compiler error reporting; improves support for making predicates listed in "uses/2" and "use_module/2" directives available as scoped predicates for the entities containing the directives; adds Handbook sections on documenting predicate exceptions and on ports and contributions distributed with Logtalk; improves Handbook sections on Prolog integration and migration; adds links from library APIs documentation to the Handbook library descriptions; adds a "genint" library supporting application global and object local named generators for increasing positive integers; updsates the "gensym" library with support for both global and object local symbol generators; adds new predicatyes to the "types" and "statistics" libraries; includes fixes and improvements to the "csv" library; adds new parametric objects to the "hook_objects" library; fixes the "arbitrary" library implementation of shrinkers when passed terms of unexpected types; includes an improved "packs" tool with new predicates, refined semantics, and support for registries that require personal token authorizations for access; fixes "lgtdoc" generated Sphinx documentation cross-referencing between applications and Logtalk distribution libraries; improves "tutor" tool feedback on sone common linter reports; fixes "diagrams" tool cases where files listed as excluded would still be included in generated diagrams; adds new tests for Logtalk and Prolog features; and includes portability updates for CxProlog, LVM, SICStus Prolog, SWI-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

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.56.0 released

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

Hi,

Logtalk 3.56.0 is now available for downloading at:

https://logtalk.org/

This release adds linter warnings for source file names and for if-then-else and soft-cut control constructs; improves the linter warnings for "findall/3" goals; adds support for calls to the database and reflection built-in methods where the predicate argument is only bound at runtime and is listed in a "uses/2" or "use_module/2" directive; fixes cases where predicate name conflicts in directives would not be reported; improves "arbitrary" library performance for several types; fixes issues with the "arbitrary" library generation of Unicode code points; provides an improved QuickCheck implementation; improves the "lgtunit" tool code coverage report format to enable reporting all test object parameterizations and files; adds linter warnings for missing documentation directives to the "lgtdoc" tool; improves performance of the "diagrams" tool; improves the documentation of libraries and tools; adds new tests and improves existing tests for Prolog standards compliance; and includes portability updates Scryer Prolog, SICStus Prolog, and Tau 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

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.55.0 released

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

Hi,

Logtalk 3.55.0 is now available for downloading at:

https://logtalk.org/

This release adds Windows PowerShell versions of the setup, integration, embedding, and tools Bash shell scripts (joint work with Hans N. Beck); includes new and improved Handbook sections; adds a library file for loading all installed packs; improves handling of file paths by the "diagrams", "lgtdoc", and "wrapper" tools; improves the documentation of the "issue_creator", "lgtunit", and "packs" tools; includes fixes and improvements for the "lgtdoc" scripts; updates the "update_html_docs.sh" and "update_svg_diagrams.sh" scripts to optionally generate packs documentation and diagrams; updates the Windows installer to copy the PowerShell integration and setup scripts to the system directory; updates documentation of the Visual Studio Code text editor Logtalk plug-in; adds new tests for official and de facto standard Prolog features; and includes portability updates Scryer Prolog, Tau Prolog, and YAP.

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] Con we do labeling/indomain with bigger numbers?

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

On 13/04/2022 16:40, Jeshan Babooa via ECLiPSe-CLP-Users wrote:
> I understood that there are certain limits concerning number ranges when using IC.
> e.g X #= 2 ^ 55, indomain(X).
> gives: out of range in indomain(X{36028797018963964 .. 36028797018963976})
> 
> This works fine in other systems like Scryer and SWI.
> 
> I was hoping to be able to label numbers of up to 2 ^ 128.
> Could this somehow work in Eclipse? hopefully in a way that doesn't need code 
> editing?
> 
> We could use several smaller integers to label them but that would meaning 
> labelling a huge number of integers.
> 
> I thought to take a look at the code and In ic.c, I saw that MAX_BITMAP_RANGE 
> could have something to do with it. When I increase it, it takes really long to 
> label just X #= 2^64.
> 
> So how should we label bigger integers?
> 
> Jeshan



Hi Jeshan,

ECLiPSe's lib(ic) constraint solver is designed for handling mixtures of real- 
and integer-valued variables and numbers. All computations in IC-constraints are 
performed using double floats to represent upper and lower bounds, and 
integrality is simply treated as an additional constraint.

Because double floats have 53 bits of precision, only integers in the range 
-9007199254740992..9007199254740992 are represented precisely. Larger integers 
are approximated by a floating point interval that encloses the true value. This 
is why your X remains uninstantiated when you exceed this range:

   ?- X #= 2 ^ 53.
   X = 9007199254740992
   Yes (0.00s cpu)

   ?- X #= 2 ^ 53 + 1.
   X = X{9007199254740991 .. 9007199254740994}
   There is 1 delayed goal.
   Yes (0.00s cpu)

It is a design decision of the IC solver to handle large numbers via this 
"fuzziness", instead of defaulting to unbounded size integer representations. 
This was done because in practice, models involving huge integer domains are 
rarely efficiently solvable, and are therefore less useful than they may seem at 
first glance.


You are not saying anything about the problem you are actually trying to solve. 
  But I suspect that your integers do not represent real world 
quantities/amounts/measurements/etc, and instead you are using them as bitmaps 
to represent arrays of booleans.   In this case I would consider modelling 
directly with boolean (0..1) variables.


-- Joachim

[eclipse-clp-users] Con we do labeling/indomain with bigger numbers?

[Jeshan B. <j...@je...>]

I understood that there are certain limits concerning number ranges when using IC.
e.g X #= 2 ^ 55, indomain(X).
gives: out of range in indomain(X{36028797018963964 .. 36028797018963976})

This works fine in other systems like Scryer and SWI.

I was hoping to be able to label numbers of up to 2 ^ 128.
Could this somehow work in Eclipse? hopefully in a way that doesn't need code editing?

We could use several smaller integers to label them but that would meaning labelling a huge number of integers.

I thought to take a look at the code and In ic.c, I saw that MAX_BITMAP_RANGE could have something to do with it. When I increase it, it takes really long to label just X #= 2^64.

So how should we label bigger integers?

Jeshan

[eclipse-clp-users] Logtalk 3.54.0 released

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

Hi,

Logtalk 3.54.0 is now available for downloading at:

https://logtalk.org/

This release
adds a new linter warning for "catch/3" goals; adds support to user-defined linter warning messages for suspicious calls; adds a new Handbook section on the logic and control built-in public methods; improves the Handbook documentation on the term-expansion mechanism; improves documentation on applying the developer tools to plain Prolog code; adds new "union_find" and "grammars" libraries; improves the "sets" library thanks to a contribution by Adrián Arroyo Calle; adds linter checks for "format/2-3" goals to the "format" library; adds new predicates to the "pairs" library; adds new types to the "arbitrary" and "types" libraries; adds a "lgtunit" tool linter check for the use of unification goals in test outcome assertions; improves the performance of the "ports_profiler" tool; includes new predicates and fixes for the "packs" tool; fixes "lgtdoc" tool issues with Sphinx output; improves and
updates examples; adds new standards compliance sets; and includes portability updates for B-Prolog, Ciao Prolog, ECLiPSe, GNU Prolog, LVM, Scryer Prolog, Tau Prolog, Trealla Prolog, and YAP.

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] Possible to suppress file compiled messages

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

Hi Joachim,

Thanks for the quick reply. I ended up using your second suggestion (set_stream/1). It works nicely.

Cheers,
Paulo

> On 21 Feb 2022, at 15:34, Joachim Schimpf <jsc...@co...> wrote:
> 
> On 21/02/2022 09:52, Paulo Moura wrote:
>> Hi,
>> I use ECLIPSe's compile/2 predicate to compile and load Prolog files. But with the default verbose:0 option (and with it explicit) I still get <file> compiled <bytes> bytes in <seconds> seconds log messages. Is there any way of suppressing these messages?
> 
> Hi Paulo,
> 
> the messages are printed by an event handler to the log_output stream.
> 
> To suppress, you can either disable the event handler with
> 
>  ?- set_event_handler(139, true/0).
> 
> or redirect the log_output stream to null
> 
>  ?- set_stream(log_output, null).
> 
> 
> Cheers,
> Joachim
> 
> 
> _______________________________________________
> ECLiPSe-CLP-Users mailing list
> ECL...@li...
> https://lists.sourceforge.net/lists/listinfo/eclipse-clp-users
> 

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

Re: [eclipse-clp-users] Possible to suppress file compiled messages

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

On 21/02/2022 09:52, Paulo Moura wrote:
> Hi,
> 
> I use ECLIPSe's compile/2 predicate to compile and load Prolog files. But with the default verbose:0 option (and with it explicit) I still get <file> compiled <bytes> bytes in <seconds> seconds log messages. Is there any way of suppressing these messages?

Hi Paulo,

the messages are printed by an event handler to the log_output stream.

To suppress, you can either disable the event handler with

   ?- set_event_handler(139, true/0).

or redirect the log_output stream to null

   ?- set_stream(log_output, null).


Cheers,
Joachim

Re: [eclipse-clp-users] Eclipse C++ examples not compiling

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

Dear Manu,

I find your mail upsetting, unfair, and completely missing the point on open source software. As the ECLiPSe license makes it clear:

7. DISCLAIMER OF WARRANTY.
COVERED CODE IS PROVIDED UNDER THIS LICENSE ON AN "AS IS'' BASIS, WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, WARRANTIES THAT THE COVERED CODE IS FREE OF DEFECTS, MERCHANTABLE, FIT FOR A PARTICULAR PURPOSE OR NON-INFRINGING. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE COVERED CODE IS WITH YOU. SHOULD ANY COVERED CODE PROVE DEFECTIVE IN ANY RESPECT, YOU (NOT THE INITIAL DEVELOPER OR ANY OTHER CONTRIBUTOR) ASSUME THE COST OF ANY NECESSARY SERVICING, REPAIR OR CORRECTION. THIS DISCLAIMER OF WARRANTY CONSTITUTES AN ESSENTIAL PART OF THIS LICENSE. NO USE OF ANY COVERED CODE IS AUTHORIZED HEREUNDER EXCEPT UNDER THIS DISCLAIMER.

You can always try to contribute a solution or use the professional support described at:

http://eclipseclp.org/commercial.html

Have you tried either option?

Cheers,
Paulo


> On 9 Oct 2021, at 12:43, Manu goswami <man...@ho...> wrote:
> 
> Hi Developers,
> 
> Eclipse clp is really creating great problems due to frequent fundamental changes causing what is perfectly working today completely breaking down next morning. Hopefully that was not the purpose of it being ‘open source’
> 
> Kindly please respond to below most urgently as a lot depends on it.
> 
> Warm regards,
> Manu
> 
> Get Outlook for iOS
> From: man...@us... <man...@us...>
> Sent: Saturday, October 9, 2021 4:17 PM
> To: kis...@us...
> Cc: man...@us...
> Subject: Eclipse C++ examples not compiling
>  
> REPLY at https://sourceforge.net/u/manugoswami/profile/send_message
> 
> Hi Mr Kish,
> 
> I am unable to compile cc examples. Illustration below
> 
> eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee
> 
> $ make eg_cc_external
> /bin/x86_64-w64-mingw32-c++ -g -D_REENTRANT -fPIC -fno-strict-overflow -Wno-logical-op-parentheses -Wno-bitwise-op-parentheses -Wno-pointer-sign -DPRINTAM -I. -I../src -I../../sys_include -isystem /usr/x86_64-w64-mingw32/sys-root/mingw/include -c ../src/eg_cc_external.cc
> cc1plus: warning: command-line option ‘-Wno-pointer-sign’ is valid for C/ObjC but not for C++
> cc1plus: note: unrecognized command-line option ‘-Wno-bitwise-op-parentheses’ may have been intended to silence earlier diagnostics
> cc1plus: note: unrecognized command-line option ‘-Wno-logical-op-parentheses’ may have been intended to silence earlier diagnostics
> /bin/x86_64-w64-mingw32-c++ -o eg_cc_external eg_cc_external.o \
> -L. -Wl,-rpath,. -leclipse \
> -L../../lib/x86_64_nt -L../../sys_lib/x86_64_nt -Wl,-rpath,../../lib/x86_64_nt \
> -lshm -L. -lgmp -lpthread -ldl -lws2_32 -lnetapi32 -lm
> /usr/bin/x86_64-w64-mingw32-ld: /usr/x86_64-w64-mingw32/sys-root/mingw/lib/../lib/libmingw32.a(lib64_libmingw32_a-crt0_c.o): in function main&#39;: /usr/src/debug/mingw64-x86_64-runtime-9.0.0-1/crt/crt0_c.c:18: undefined reference toWinMain'
> collect2: error: ld returned 1 exit status
> make: *** [Makefile:312: eg_cc_external] Error 1
> 
> manugoswami@S01395MANU /cygdrive/d/ons_1/ons_eclipse/ons_eclipse_7055/kernel/x86_64_nt
> $ make eg_cc_test.cc
> make: Nothing to be done for '../src/eg_cc_test.cc'.
> 
> manugoswami@S01395MANU /cygdrive/d/ons_1/ons_eclipse/ons_eclipse_7055/kernel/x86_64_nt
> $ make eg_cc_test
> /bin/x86_64-w64-mingw32-c++ -g -D_REENTRANT -fPIC -fno-strict-overflow -Wno-logical-op-parentheses -Wno-bitwise-op-parentheses -Wno-pointer-sign -DPRINTAM -I. -I../src -I../../sys_include -isystem /usr/x86_64-w64-mingw32/sys-root/mingw/include -c ../src/eg_cc_test.cc
> cc1plus: warning: command-line option ‘-Wno-pointer-sign’ is valid for C/ObjC but not for C++
> In file included from /lib/gcc/x86_64-w64-mingw32/11/include/c++/ext/string_conversions.h:41,
> from /lib/gcc/x86_64-w64-mingw32/11/include/c++/bits/basic_string.h:6607,
> from /lib/gcc/x86_64-w64-mingw32/11/include/c++/string:55,
> from /lib/gcc/x86_64-w64-mingw32/11/include/c++/bits/locale_classes.h:40,
> from /lib/gcc/x86_64-w64-mingw32/11/include/c++/bits/ios_base.h:41,
> from /lib/gcc/x86_64-w64-mingw32/11/include/c++/ios:42,
> from /lib/gcc/x86_64-w64-mingw32/11/include/c++/ostream:38,
> from /lib/gcc/x86_64-w64-mingw32/11/include/c++/iostream:39,
> from ../src/eg_cc_test.cc:37:
> /lib/gcc/x86_64-w64-mingw32/11/include/c++/cstdlib:75:15: fatal error: stdlib.h: No such file or directory
> 75 | #include_next <stdlib.h>
> | ^~~~~~~~~~
> compilation terminated.
> make: *** [Makefile:210: eg_cc_test.o] Error 1
> 
> Warm Regards,
> Manu
> 
> This message was sent to you via the SourceForge web mail form.
> Replying to this email will not work, please send a message to Manu Goswami at https://sourceforge.net/u/manugoswami/profile/send_message
> 
> _______________________________________________
> ECLiPSe-CLP-Users mailing list
> ECL...@li...
> https://lists.sourceforge.net/lists/listinfo/eclipse-clp-users

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

[eclipse-clp-users] Possible to suppress file compiled messages

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

Hi,

I use ECLIPSe's compile/2 predicate to compile and load Prolog files. But with the default verbose:0 option (and with it explicit) I still get <file> compiled <bytes> bytes in <seconds> seconds log messages. Is there any way of suppressing these messages?

Thanks,
Paulo 

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

[eclipse-clp-users] Logtalk 3.53.0 released

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

Hi,

Logtalk 3.53.0 is now available for downloading at:

https://logtalk.org/

This release includes a new developer tool, "issue_creator", for automatically creating bug report issues for failed tests in GitHub or GitLab servers; adds support for using object aliases in the message delegation control construct; adds a Handbook section on calling Prolog foreign predicates; includes documentation fixes and improvements; adds new predicates to the "options" library; fixes a bug in the "intervals" library; updates the "logtalk_tester" automation script to use the new "issue_creator" tool; includes improvements to the "packs" tool; updates the "metagol" port; adds new test sets and tests for Prolog standards compliance; updates support for a new version of the Visual Studio Code text editor Logtalk plug-in; and includes portability updates for Ciao Prolog, GNU Prolog, LVM, SICStus Prolog, SWI-Prolog, Trealla Prolog, and YAP.

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.52.0 released

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

Hi,

Logtalk 3.52.0 is now available for downloading at:

https://logtalk.org/

This release fixes compiler and linter issues; includes an improved version of the new "packs" tool, a portable and decentralized package manager; adds new "dif" and "format" abstraction libraries; updates the "hook_objects", "os", and "types" libraries; includes documentation updates to the Handbook, tools, man pages, and scripts; includes fixes and improvements for the "debugger", "diagrams", "lgtunit", and "tutor" tools; updates several programming examples; provides additional Prolog standards compliance tests; provides additional Logtalk tests; and includes portability updates for GNU Prolog, LVM, Tau Prolog, Trealla Prolog, XSB, and YAP.

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] A portable and decentralized package manager for sharing Logtalk and Prolog resources

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

Hi,

The recently released Logtalk 3.51.0 version includes a beta version of the new "packs" tool, a portable and decentralized package manager for sharing Logtalk and Prolog resources:

https://logtalk.org/manuals/devtools/packs.html

This tool allows anyone wishing to share their work to setup a pack registry allowing users to easily install and update those resources. Some of those pack registries are indexed at:

https://github.com/LogtalkDotOrg/pack-registries

The "packs" tool runs on most of the Logtalk supported backend Prolog systems (see the "Known issues" section in the first link above for current exceptions). When installing Prolog packs, Logtalk is only required to run the tool.

The tool includes documentation and linter support for defining new registry and pack specifications. Feedback is most welcome. Let us know if you setup a public pack registry.

Enjoy,
Paulo

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

[eclipse-clp-users] Logtalk 3.51.0 released

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

Hi,

Logtalk 3.51.0 is now available for downloading at:

https://logtalk.org/

This release includes a beta version of the new "packs" tool, a portable and decentralized package manager; provides new "lgtunit" test outcomes and new input/output testing predicates; improves the compilation of large test sets by generating more compact code; improves the generation of Allure testing reports to include crashed and broken test sets; includes improved man pages to the testing scripts; includes "lgtdoc" tool bug fixes; improves the "make" tool; includes new "csv" library predicates; updates the os library for some backends; improves some of the programming examples; includes additional tests for Prolog compliance; fixes a Windows installer bug with settings files; and includes portability updates for all backends, notably by providing implementations of the atomic_concat/3 and atomic_list_concat/2-3 predicates.

Thanks to Paul Brown, Michael T. Richter, and Doug Kearns 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

[eclipse-clp-users] Logtalk 3.50.0 released

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

Hi,

Logtalk 3.51.0 is now available for downloading at:

https://logtalk.org/

This release includes a beta version of the new "packs" tool, a portable and decentralized package manager; provides new "lgtunit" test outcomes and new input/output testing predicates; improves the compilation of large test sets by generating more compact code; improves the generation of Allure testing reports to include crashed and broken test sets; includes improved man pages to the testing scripts; includes "lgtdoc" tool bug fixes; improves the "make" tool; includes new "csv" library predicates; updates the os library for some backends; improves some of the programming examples; includes additional tests for Prolog compliance; fixes a Windows installer bug with settings files; and includes portability updates for all backends, notably by providing implementations of the atomic_concat/3 and atomic_list_concat/2-3 predicates.

Thanks to Paul Brown, Michael T. Richter, and Doug Kearns 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] Eclipse C++ examples not compiling

[Manu g. <man...@ho...>]

Hi Developers,

Eclipse clp is really creating great problems due to frequent fundamental changes causing what is perfectly working today completely breaking down next morning. Hopefully that was not the purpose of it being ‘open source’

Kindly please respond to below most urgently as a lot depends on it.

Warm regards,
Manu

Get Outlook for iOS<https://aka.ms/o0ukef>
________________________________
From: man...@us... <man...@us...>
Sent: Saturday, October 9, 2021 4:17 PM
To: kis...@us...
Cc: man...@us...
Subject: Eclipse C++ examples not compiling


REPLY at https://sourceforge.net/u/manugoswami/profile/send_message

________________________________

Hi Mr Kish,

I am unable to compile cc examples. Illustration below

eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee

$ make eg_cc_external
/bin/x86_64-w64-mingw32-c++ -g -D_REENTRANT -fPIC -fno-strict-overflow -Wno-logical-op-parentheses -Wno-bitwise-op-parentheses -Wno-pointer-sign -DPRINTAM -I. -I../src -I../../sys_include -isystem /usr/x86_64-w64-mingw32/sys-root/mingw/include -c ../src/eg_cc_external.cc
cc1plus: warning: command-line option ‘-Wno-pointer-sign’ is valid for C/ObjC but not for C++
cc1plus: note: unrecognized command-line option ‘-Wno-bitwise-op-parentheses’ may have been intended to silence earlier diagnostics
cc1plus: note: unrecognized command-line option ‘-Wno-logical-op-parentheses’ may have been intended to silence earlier diagnostics
/bin/x86_64-w64-mingw32-c++ -o eg_cc_external eg_cc_external.o \
-L. -Wl,-rpath,. -leclipse \
-L../../lib/x86_64_nt -L../../sys_lib/x86_64_nt -Wl,-rpath,../../lib/x86_64_nt \
-lshm -L. -lgmp -lpthread -ldl -lws2_32 -lnetapi32 -lm
/usr/bin/x86_64-w64-mingw32-ld: /usr/x86_64-w64-mingw32/sys-root/mingw/lib/../lib/libmingw32.a(lib64_libmingw32_a-crt0_c.o): in function main&#39;: /usr/src/debug/mingw64-x86_64-runtime-9.0.0-1/crt/crt0_c.c:18: undefined reference toWinMain'
collect2: error: ld returned 1 exit status
make: *** [Makefile:312: eg_cc_external] Error 1

manugoswami@S01395MANU /cygdrive/d/ons_1/ons_eclipse/ons_eclipse_7055/kernel/x86_64_nt
$ make eg_cc_test.cc
make: Nothing to be done for '../src/eg_cc_test.cc'.

manugoswami@S01395MANU /cygdrive/d/ons_1/ons_eclipse/ons_eclipse_7055/kernel/x86_64_nt
$ make eg_cc_test
/bin/x86_64-w64-mingw32-c++ -g -D_REENTRANT -fPIC -fno-strict-overflow -Wno-logical-op-parentheses -Wno-bitwise-op-parentheses -Wno-pointer-sign -DPRINTAM -I. -I../src -I../../sys_include -isystem /usr/x86_64-w64-mingw32/sys-root/mingw/include -c ../src/eg_cc_test.cc
cc1plus: warning: command-line option ‘-Wno-pointer-sign’ is valid for C/ObjC but not for C++
In file included from /lib/gcc/x86_64-w64-mingw32/11/include/c++/ext/string_conversions.h:41,
from /lib/gcc/x86_64-w64-mingw32/11/include/c++/bits/basic_string.h:6607,
from /lib/gcc/x86_64-w64-mingw32/11/include/c++/string:55,
from /lib/gcc/x86_64-w64-mingw32/11/include/c++/bits/locale_classes.h:40,
from /lib/gcc/x86_64-w64-mingw32/11/include/c++/bits/ios_base.h:41,
from /lib/gcc/x86_64-w64-mingw32/11/include/c++/ios:42,
from /lib/gcc/x86_64-w64-mingw32/11/include/c++/ostream:38,
from /lib/gcc/x86_64-w64-mingw32/11/include/c++/iostream:39,
from ../src/eg_cc_test.cc:37:
/lib/gcc/x86_64-w64-mingw32/11/include/c++/cstdlib:75:15: fatal error: stdlib.h: No such file or directory
75 | #include_next <stdlib.h>
| ^~~~~~~~~~
compilation terminated.
make: *** [Makefile:210: eg_cc_test.o] Error 1

________________________________

Warm Regards,
Manu

________________________________

This message was sent to you via the SourceForge web mail form.
Replying to this email will not work, please send a message to Manu Goswami at https://sourceforge.net/u/manugoswami/profile/send_message