factlist bug

[Broes De Cat]

What are the expected semantics? Currently: all occurring atoms are supposed to be two-valued

Less error-prone would be: everything in the structure's vocabulary is two-valued?

[Bart Bogaerts]

The disadvantage is that this way, the user is obligated to use subvocabularies...

maybe throw a warning: only symbols .... are interpreted?

[Broes De Cat]

In the asp-competition, the list of input symbols is known. Now however, if such an input symbol does not occur in the factlist of an instance, it is interprted completely unknown instead of completely false. A warning would not help it in this case.

[Bart Bogaerts]

agree.

[Joachim Jansen]

When closing ASP structures, make all symbols two-valued also for empty interpretations

This is done by making all unknowns false for each non-built-in symbol in the vocabulary of the structure that is being closed.

This fixes bug #459

→ <<cset 4a2fa1075df3>>

[Joachim Jansen]

When closing ASP structures, make all symbols two-valued also for empty interpretations

This is done by making all unknowns false for each non-built-in symbol in the vocabulary of the structure that is being closed.

This fixes bug #459

→ <<cset f1b62f0f490e>>

[Broes De Cat]

When closing ASP structures, make all symbols two-valued also for empty interpretations

This is done by making all unknowns false for each non-built-in symbol in the vocabulary of the structure that is being closed.

This fixes bug #459

→ <<cset b83000009333>>