Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Nov 28 22:23

    pmoura on master

    Additional test for the `use_mo… (compare)

  • Nov 27 23:42

    pmoura on master

    Fix explicit messages to the `u… (compare)

  • Nov 27 23:08

    pmoura on master

    Update the `figures` example to… (compare)

  • Nov 27 10:58

    pmoura on master

    Add support for XSB to the `cor… Update SVG diagrams (compare)

  • Nov 26 16:39

    pmoura on master

    Cleanup XSB adapter file (this … (compare)

  • Nov 26 08:32

    pmoura on master

    Fix new tests of the `hook_obje… (compare)

  • Nov 25 18:03

    pmoura on master

    Add missing `cleanup/0` predica… (compare)

  • Nov 25 17:54

    pmoura on master

    Additional tests for the `forma… (compare)

  • Nov 25 16:13

    pmoura on master

    Update `diagrams` tool `lgt2svg… (compare)

  • Nov 25 14:36

    pmoura on master

    Improve man pages of the integr… (compare)

  • Nov 25 11:17

    pmoura on master

    Change `diagrams` tool `dot` gr… (compare)

  • Nov 24 22:15

    pmoura on master

    Add tests for the new `object_w… Add `cleanup/0` predicate defin… (compare)

  • Nov 24 22:07

    pmoura on master

    Add `object_wrapper_hook/1` obj… (compare)

  • Nov 24 19:10

    pmoura on master

    Improve man pages of the integr… (compare)

  • Nov 24 14:32

    pmoura on master

    Update notes on optional featur… (compare)

  • Nov 24 10:29

    pmoura on lvm_cyclic

    Set LVM adapter file value for … (compare)

  • Nov 23 23:57

    pmoura on lvm_coroutining

    Additional tests for the `corou… Merge branch 'master' into lvm_… (compare)

  • Nov 23 23:56

    pmoura on master

    Additional tests for the `corou… (compare)

  • Nov 23 23:51

    pmoura on lvm_coroutining

    Additional tests for the `corou… Merge branch 'master' into lvm_… (compare)

  • Nov 23 23:51

    pmoura on master

    Additional tests for the `corou… (compare)

A Man With A Clever Disguise
@ACleverDisguise
Yes, or my tests.
Paulo Moura
@pmoura
logtalk_load([dictionaries(loader),types(loader)], [optimize(on), debug(off)]) can simply be logtalk_load([dictionaries(loader),types(loader)]).
A Man With A Clever Disguise
@ACleverDisguise
It defaults to optimize and no debug?
I tend to over-specify to establish intent.
Paulo Moura
@pmoura
No. But the loader files for those libraries already ensure they are compiled in optimized mode.
Is two2tree a single file or a loader file?
A Man With A Clever Disguise
@ACleverDisguise
A single file for now.
OK, I found the path.
Paulo Moura
@pmoura
Ok.
?
A Man With A Clever Disguise
@ACleverDisguise
If I load the tester.lgt by itself the flag is clear because of course it is.
I need to load debug first, then tester, to have the debug flag set.
Paulo Moura
@pmoura
It may be simpler to remove the calls to set_logtalk_flag(debug,on) from those initialization directives and just call this goal at the top-level (assuming here you're doing interactive debugging) when you want to see the debug messages.
A Man With A Clever Disguise
@ACleverDisguise
Probably, yes.
Well, when I'm debugging I will always want to see them. It's when I run just the tester that I'll do it manually.
Paulo Moura
@pmoura
You can always have multiple loader files, e.g. loader.lgt, loader_debug.lgt, ...
A Man With A Clever Disguise
@ACleverDisguise
I was trying to be too tricky for my own good by having a root loader that gets modified depending on if I want to debug, test, etc.
I'll just stop trying to be too DRY.
It's not as if these scripts change a lot.
Paulo Moura
@pmoura
Your loader_debug.lgt file can simply do logtalk_load(loader) +set_logtalk_flag(debug,on)` + ... so you would still use a single root loader file and derive from it in a minmal way.
A Man With A Clever Disguise
@ACleverDisguise
OK, we're back to this.
debug is on, manually confirmed.
Not a single print_message in the debug domain got printed.
If I change it to information, they all get printed.
So even manually turning the debug flag on before loading the tester still gives me tests that don't display debug messages.
Paulo Moura
@pmoura
You can use the object_property/2 predicate to check the properties of the object containing those calls.
A Man With A Clever Disguise
@ACleverDisguise
Not sure what I'm checking for? debugging is set, among a host of others that don't seem relevant.
Paulo Moura
@pmoura
Contents of the tester.lgt file?
A Man With A Clever Disguise
@ACleverDisguise
:- initialization((
    set_logtalk_flag(report, warnings),
    logtalk_load(loader),
    logtalk_load(lgtunit(loader)),
    logtalk_load(two3tree, [source_data(on), debug(on)]),
    logtalk_load(tests, [hook(lgtunit)]),
    tests::run
)).
Paulo Moura
@pmoura
And the debug message printing calls are in the two2three file?
A Man With A Clever Disguise
@ACleverDisguise
tests file right now.
I'm trying to nail down a problem in the validation predicates in the tests.
Paulo Moura
@pmoura
Can you paste one of the clauses that contain the print message call?
A Man With A Clever Disguise
@ACleverDisguise

First the uses clause that gives me the message in a convenient format. Currently set to information but if I change it to debug it never prints anything.

    :- uses(logtalk, [print_message(information, two3tree_tests, Message) as dbg(Message)]).

Now a typical clause:

    depth(Din, node(L, _, R), Dout) :-
        depth(L, DL),
        depth(R, DR),
        DL == DR, % if the depths don't match, this is a big problem!
        Dout is  Din + DL,
        dbg(depth-(Dout-node2_descend)).
Paulo Moura
@pmoura
That clause is not calling dbg/1. You meant to paste a different one?
A Man With A Clever Disguise
@ACleverDisguise
So that uses clause works. Messages print. But without changing anything else in the code, and after manually turning the debug flag on and confirming it's on, changing it to debug makes it stop working.
Oh, right. Sorry.
Fixed.
I took a test, not a helper. :)
Paulo Moura
@pmoura
Is the dbg/1 call ever reached?
A Man With A Clever Disguise
@ACleverDisguise
If I switch it to information it displays, so yes.
Paulo Moura
@pmoura
I assume so?
A Man With A Clever Disguise
@ACleverDisguise
% depth: 1-node2_leaf
% depth: 1-node(leaf,10-value10,leaf)
% two3tree_insert_1: success (in 0.0004346110000001957 seconds)
% depth: 1-node3_leaf
% depth: 1-node(leaf,10-value10,leaf,20-value20,leaf)
% two3tree_insert_2: success (in 0.00041456800000005956 seconds)
Test output for a successful test.
Paulo Moura
@pmoura
And if you modify that clause to print the value of the debug flag?
A Man With A Clever Disguise
@ACleverDisguise

OK, so I'll give you two results. Here's the run with dbg/1 using information:

% depth: 1-node2_leaf
% on
% depth: 1-node(leaf,10-value10,leaf)
% two3tree_insert_1: success (in 0.00029869099999979554 seconds)
% depth: 1-node3_leaf
% depth: 1-node(leaf,10-value10,leaf,20-value20,leaf)
% two3tree_insert_2: success (in 0.0002536849999996704 seconds)

And here's the run with dbg/1 using debug on the same test results:

% on
% two3tree_insert_1: success (in 0.00033641100000014745 seconds)
% two3tree_insert_2: success (in 0.00021322999999995318 seconds)
The dbg/1 messages vanish if configured for debug but are visible if configured for information. In both cases the current_logtalk_flag (displayed using print_message/3 using information always) is on.
A Man With A Clever Disguise
@ACleverDisguise
Adding this to the tests object doesn't change anything:
    :- set_logtalk_flag(debug, on).
Paulo Moura
@pmoura
I think I have enough details from you to look into it. Possible tomorrow.
A Man With A Clever Disguise
@ACleverDisguise
It's not critical, just to be clear. I'm fine with using information class. I was just wondering if there was something I was missing.
Paulo Moura
@pmoura
Not clear at this time. Nothing obviously wrong. But I have meetings all day and can't look at it today.