1. KRR Avatar KRR
  2. software
  3. IDP
  4. Issues

XSB Definition evaluation incorrect when a variable ranges over a stricter type

Issue #642 resolved
Joachim Jansen created an issue

Attached file does not result in a correct model.

Comments (2)

  2. Joachim Jansen reporter

    Added extra type check after each XSB predicate call

    This is because any variable that was instantiated in that call might actually range over a different/stricter domain.

    This type check could be filtered out if one could detect what the types of the predicate call were. Doing this at this stage would incur heavy refactoring, since a PrologTerm has no notion of the type of it's called variables.

    This fixes bug #642

    → <<cset 9b83c9beea71>>

  3. Log in to comment
Assignee
Type
bug
Priority
major
Status
resolved
Component
XSB
Version
–
Votes
0
Watchers
1
Jira: the preferred issue tracker for Bitbucket. Join the team!