XSB prevents calculation of definition
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)
-
-
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>>
-
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>>
-
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>>
-
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>>
-
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>>
-
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>>
-
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>>
-
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>>
-
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>>
- Log in to comment
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