XSB prevents calculation of definition

Issue #826 resolved
Ingmar Dasseville created an issue

http://seldon.cs.kuleuven.be/idp/?src=d8535d1613e145d10271

XSB off: gcd -> OK theory + gcd -> OK

XSB ON: gcd -> OK theory + gcd -> NOT OK

Comments (10)

  1. Joachim Jansen

    error in stdoptions.joindefsforxsb

    when this is turned off, file runs fine.

    So joining the defs results in some problems. I'm looking into it

  2. Joachim Jansen

    Fixed bootstrapping tactic for joining definitions before sending them to XSB

    Previously, no attention was given to the fact whether the newly generated definition was calculable (= calculatedefinitions would be appliccable)

    Perhaps a TODO would be to drop this constraint for definition refinement, but to keep it for definition evaluation.

    This fixes issue #826

    → <<cset 8808df8dce90>>

  3. Joachim Jansen

    Fixed bootstrapping tactic for joining definitions before sending them to XSB

    Previously, no attention was given to the fact whether the newly generated definition was calculable (= calculatedefinitions would be appliccable)

    Perhaps a TODO would be to drop this constraint for definition refinement, but to keep it for definition evaluation.

    This fixes issue #826

    → <<cset 18572c29447d>>

  4. Joachim Jansen

    Fixed bootstrapping tactic for joining definitions before sending them to XSB

    Previously, no attention was given to the fact whether the newly generated definition was calculable (= calculatedefinitions would be appliccable)

    Perhaps a TODO would be to drop this constraint for definition refinement, but to keep it for definition evaluation.

    This fixes issue #826

    → <<cset f309320a3edb>>

  5. Ingmar Dasseville reporter

    Fixed bootstrapping tactic for joining definitions before sending them to XSB

    Previously, no attention was given to the fact whether the newly generated definition was calculable (= calculatedefinitions would be appliccable)

    Perhaps a TODO would be to drop this constraint for definition refinement, but to keep it for definition evaluation.

    This fixes issue #826

    → <<cset f309320a3edb>>

  6. Bart Bogaerts

    Fixed bootstrapping tactic for joining definitions before sending them to XSB

    Previously, no attention was given to the fact whether the newly generated definition was calculable (= calculatedefinitions would be appliccable)

    Perhaps a TODO would be to drop this constraint for definition refinement, but to keep it for definition evaluation.

    This fixes issue #826

    → <<cset 0229c070ca66>>

  7. Joachim Jansen

    Fixed bootstrapping tactic for joining definitions before sending them to XSB

    Previously, no attention was given to the fact whether the newly generated definition was calculable (= calculatedefinitions would be appliccable)

    Perhaps a TODO would be to drop this constraint for definition refinement, but to keep it for definition evaluation.

    This fixes issue #826

    → <<cset 222ed698c512>>

  8. Joachim Jansen

    Fixed bootstrapping tactic for joining definitions before sending them to XSB

    Previously, no attention was given to the fact whether the newly generated definition was calculable (= calculatedefinitions would be appliccable)

    Perhaps a TODO would be to drop this constraint for definition refinement, but to keep it for definition evaluation.

    This fixes issue #826

    → <<cset 92868c5191b1>>

  9. Joachim Jansen

    Fixed bootstrapping tactic for joining definitions before sending them to XSB

    Previously, no attention was given to the fact whether the newly generated definition was calculable (= calculatedefinitions would be appliccable)

    Perhaps a TODO would be to drop this constraint for definition refinement, but to keep it for definition evaluation.

    This fixes issue #826

    → <<cset 08ae7d1afda3>>

  10. Matthias van der Hallen

    Fixed bootstrapping tactic for joining definitions before sending them to XSB

    Previously, no attention was given to the fact whether the newly generated definition was calculable (= calculatedefinitions would be appliccable)

    Perhaps a TODO would be to drop this constraint for definition refinement, but to keep it for definition evaluation.

    This fixes issue #826

    → <<cset 08ae7d1afda3>>

  11. Log in to comment