Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo


#9 update clause plan documentation

Kevin Quick

The documentation implies that a "step n" or "as" directive must be supplied for bc-rule clause plans, but it appears to be sufficient to simply provide the plan statements without this specification.

In addition, I frequently encountered a complaint that there was no plan for a clause. This was usually because a clause in whatever rule was selected to prove that clause had a plan but the current clause had no plan. It took quite some time to puzzle out that this was the reason for this "no plan in clause N" error. Better documentation would help a lot here, although I wonder if it would be appropriate to automatically generate '$$()' or 'return $$()' plans for these clauses? As it is, deciding to add a plan to a clause somewhere near a leaf of the proof tree can have a fairly significant ripple effect here.

It wasn't obvious that python clauses can't have a plan (maybe it was stated and I overlooked it).


    • status: open --> closed-fixed
  • Logged In: YES
    Originator: NO

    I've extensively rewritten the following documentation pages to try to clarify these issues: Overview -> Plans, Overview -> Knowledge Bases -> Rule Bases and KRB Syntax -> Bc_rule.

    I've placed your suggestion to automatically generate '$$()' or 'return $$()' plan specs into the Feature Request Tracker. It is #1864021 if you want to monitor it. I'll have to think about how to implement this...

    Fixed in svn revision 55. Will be incorporated into alpha 2 release.