When a term passes through term_expansion/2 trying to debug/understand the term expansion can be challenging at first. One effective aid in debugging term_expansion/2 is using debug/3 with listing/1 . Here is a very simple module with term_expansion/2 and debug/3. Note: This is in a file C:/direct…

The other tip: if goal/term expansion doesn’t do what you want, just call it explicitly using the term you want to see expanded. That way you can easily trace it the usual way.

[image] jan: if goal/term expansion doesn’t do what you want, just call it explicitly using the term you want to see expanded. Yes that was the approach I originally tried with EDCG but the problem I ran into and am still unable to solve is that EDCG has some initialization facts that are us…

[image] EricGT: … so EDCG does not see the code in a test as a separate module and thus the initialization facts are not seen as being unique to each module/test. Given that the “initialization facts” are clauses for multifile predicates, they are shared and never “unique to each module/test”…

[image] pmoura: The Logtalk port of EDCGs doesn’t use multifile predicates and its alternative expansion solution could also be used in the SWI-Prolog port. It seems that logtalk uses module-local predicates acc_info/{5,7},pred_info/3, and pass_info/{1,2}. I can see that pred_info/3 makes sen…

Object-local, not module-local. :stuck_out_tongue: You have a minor typo in your reply: acc_info/{5,5} should be acc_info/{5,7}. Not sure I understand your question, however. All those predicates are used in the expansion of an EDCG. Even if, in some particular case, some of them are shared betwee…

(Fixed the typo) Multiple modules/objects could use the same accumulators … would you simply put the acc_info{5,7} into its own module (presumably with the accumulator predicate) and then import it wherever used? (The pred_info predicates would be “object-local”.)

In my current port, importing (from a module) will not work as the clauses need to be local in order to be term-expanded. Predicates that are visible locally due to an import are not visible to the term-expansion mechanism as they are not part of the source file being expanded. A sharing solution th…

Simple term_expansion debugging

Nice to know

EricGT August 1, 2020, 1:03pm 9

Jan W. has some useful details here.

Topic		Replies	Views
How to define an exportable term_expansion/2? Help! how-to	12	780	January 17, 2022
Sharing term expansion across modules Help!	53	1566	June 6, 2021
Strange warning message from compile or listing Help! bug	10	762	July 26, 2021
Package edcg needs module predicates to work, is there another abstraction level possible? Pack	30	955	March 4, 2022
Multi-pass compilation? (for term expansion) Tools	14	1054	April 23, 2020

Simple term_expansion debugging

Related topics