Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • 19:51

    pmoura on master

    Add `packs` tool `readme/2` pre… (compare)

  • 16:33

    pmoura on master

    Update API documentation and SV… Refactor of the registries/pack… (compare)

  • 10:11

    pmoura on master

    Update `packs` tool documentati… (compare)

  • 00:55

    pmoura on master

    Update `packs` tool documentati… (compare)

  • Oct 16 23:58

    pmoura on master

    Update `packs` tool documentati… (compare)

  • Oct 16 23:43

    pmoura on master

    Change the SICStus Prolog adapt… Improve `packs` tool checking f… (compare)

  • Oct 16 18:38

    pmoura on master

    Add `packs::search/1` predicate (compare)

  • Oct 16 13:52

    pmoura on master

    Update `packs` tool documentati… Update Trealla Prolog adapter f… (compare)

  • Oct 16 08:55

    pmoura on master

    Better ordering of `packs` and … Update SVG diagrams (compare)

  • Oct 16 08:37

    pmoura on master

    Add `packs::dependents/1-3` pre… (compare)

  • Oct 15 21:30

    pmoura on master

    Fix test for the `logtalk_libra… (compare)

  • Oct 15 13:54

    pmoura on master

    Add section on best practices t… (compare)

  • Oct 15 13:28

    pmoura on master

    Added `packs::available/1` pred… (compare)

  • Oct 15 10:38

    pmoura on master

    Add alpha version of the new `p… Update SVG diagrams (compare)

  • Oct 15 10:37

    pmoura on packs

    Add alpha version of the new `p… Update SVG diagrams (compare)

  • Oct 15 09:53

    pmoura on packs

    Allow registries to be pinned Add section on security conside… (compare)

  • Oct 15 08:43

    pmoura on packs

    Print registry and pack path to… (compare)

  • Oct 14 21:02

    pmoura on packs

    Minor update to the `packs` too… (compare)

  • Oct 14 20:33

    pmoura on packs

    Improve some of the `packs` too… (compare)

  • Oct 14 20:23

    pmoura on packs

    Rename `packs::delete/1-2` pred… Update SVG diagrams (compare)

Paulo Moura
@pmoura
Follow the bread crumps on that tweet for a demo...
A Man With A Clever Disguise
@ACleverDisguise
% 
% tests started at 2021-09-10, 23:37:45
% 
% running tests from object tests
% file: /home/michael/src/Playthings/Prolog/Logtalk/two3tree/tests.lgt
% 
% two3tree_new: success (in 0.0001542940000001103 seconds)
% two3tree_insert_1: success (in 0.00011241300000008891 seconds)
% two3tree_insert_2: success (in 0.0001055439999997354 seconds)
% two3tree_insert_3: success (in 0.0004157660000001506 seconds)
% two3tree_insert_4: success (in 0.0001568519999999296 seconds)
% two3tree_insert_5: success (in 0.00012946400000002356 seconds)
% two3tree_insert_6: success (in 0.00017247299999967325 seconds)
% two3tree_insert_7: success (in 0.00018493100000016582 seconds)
% 
% 8 tests: 0 skipped, 8 passed, 0 failed (0 flaky)
% completed tests from object tests
% 
% no code coverage information collected
% tests ended at 2021-09-10, 23:37:45
%
Just the kind of report I like to see. :D
Paulo Moura
@pmoura
👍
A Man With A Clever Disguise
@ACleverDisguise
I'm going to have to learn to power-use the debugger so that I can phase out dbg/1 messages.
Paulo Moura
@pmoura
You're missing cover(two3tree). clause in the testsobject.
(assuming that two3tree is the name of the object being tested)
A Man With A Clever Disguise
@ACleverDisguise
I had it commented out to declutter the display while there were errors showing.
Paulo Moura
@pmoura
Ah, ok.
A Man With A Clever Disguise
@ACleverDisguise
% 
% tests started at 2021-09-10, 23:42:04
% 
% running tests from object tests
% file: /home/michael/src/Playthings/Prolog/Logtalk/two3tree/tests.lgt
% 
% two3tree_new: success (in 0.0001543320000001458 seconds)
% two3tree_insert_1: success (in 0.00010364400000018037 seconds)
% two3tree_insert_2: success (in 0.00011810099999998158 seconds)
% two3tree_insert_3: success (in 0.0004362789999996508 seconds)
% two3tree_insert_4: success (in 0.00013675199999996224 seconds)
% two3tree_insert_5: success (in 0.00012492799999996862 seconds)
% two3tree_insert_6: success (in 0.00015842699999968346 seconds)
% two3tree_insert_7: success (in 0.0001948069999997415 seconds)
% 
% 8 tests: 0 skipped, 8 passed, 0 failed (0 flaky)
% completed tests from object tests
% 
% 
% clause coverage ratio and covered clauses per entity predicate
% 
% two3tree: empty/1 - 1/1 - (all)
% two3tree: insert/4 - 4/4 - (all)
% two3tree: new/1 - 1/1 - (all)
% two3tree: node4/1 - 0/1 - []
% two3tree: 6 out of 7 clauses covered, 85.714286% coverage
% 
% 1 entity declared as covered containing 7 clauses
% 1 out of 1 entity covered, 100.000000% entity coverage
% 6 out of 7 clauses covered, 85.714286% clause coverage
% 
% tests ended at 2021-09-10, 23:42:04
%
Better?
Paulo Moura
@pmoura
Good coverage. You can also easily generate a report for that. E.g. https://logtalk.org/diagrams/coverage_report.html
A Man With A Clever Disguise
@ACleverDisguise
Well, I'm very deliberately writing the tree code and the tests piecemeal, making sure that my tests are valid for each case before moving up the case ladder.
So the coverage is always going to be one or two clauses uncovered at most.
I wish I had more time to do Logtalk.
This is a whole lot more fun than C. About in the same league as Ada, but for entirely different reasons.
A Man With A Clever Disguise
@ACleverDisguise
I have one more case to contend with and then insertion is complete.
After that the low-hanging fruit of searches, iteration, etc. is in the cards. That should be trivial. (I've done most of the work needed in the tester helpers for validating the tree structure.)
Once that's done, the Big One: deletion.
That's a real pig of an operation in 2-3 trees.
A lot of libraries that do 2-3 trees don't do deletion, but I suspect it will be easier in a declarative language than an imperative.
Paulo Moura
@pmoura
It should be possible to evolve your implementation so that it would eventaully comply with the dictionaries library protocol.
A Man With A Clever Disguise
@ACleverDisguise
That is the plan.
:- object(two3tree, implements(dictionaryp),
                    extends(term)).
…
Paulo Moura
@pmoura
👍
Paulo Moura
@pmoura
Got a short break and tried to reproduce the bug with the dbg/1 calls. No luck so far. It works fine in my experiments.
With the debug flag turned off, I call tests::run. No debug messages. I turn of the flag, run the tests again and get debug messages. Tried with dbg/1 calls from cleanup/0, tests, and test auxiliary predicates.
Paulo Moura
@pmoura
No chance that you're typing set_prolog_flag instead of set_logtalk_flag?
A Man With A Clever Disguise
@ACleverDisguise
Nope. Definitely typing set_logtalk_flag. And using current_logtalk_flag to get the setting.
Paulo Moura
@pmoura
You will need to provide all the necessary code and steps to reproduce the issue then.
A Man With A Clever Disguise
@ACleverDisguise
Will do. Probably on the weekend, though. I don't have a huge amount of time in the week to do things anymore. :-/
Paulo Moura
@pmoura
Resumed work on the Logtalk package manager. Details at https://github.com/LogtalkDotOrg/logtalk3/discussions/118