Limit XOR and IFF to two arguments #59
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Currently, XOR and IFF are specified as n-ary connectives. In addition to being rarely used, these connectives are not intuitive in their associative, n-ary forms. For example, a naive user may confuse XOR with natural 'either .. or', which doesn't hold with more than 2 args; it is rather 'odd' (pun intended :)). I think those FTA tools that do support these gates limit the number of arguments to 2 (e.g., graphically). It would be unreasonable to require generality without a practical need.
|
I agree totally. Never seen the use of un XOR with more than 2 args. Moreover there to 2 ways defined it (either one and only one, or parity) |
rakhimov
added a commit
to rakhimov/scram
that referenced
this pull request
Jan 23, 2018
These connectives are not intuitive with more than 2 args. More reasoning: open-psa/mef#59 Issue #231
rakhimov
added a commit
to rakhimov/scram
that referenced
this pull request
Jan 23, 2018
These connectives are not intuitive with more than 2 args. More reasoning: open-psa/mef#59 Issue #232
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently, XOR and IFF are specified as n-ary connectives.
Besides being rarely used/needed,
these connectives are not intuitive in their associative, n-ary forms.
For example, a naive user may confuse XOR with natural 'either .. or',
which doesn't hold with more than 2 args;
it is rather 'odd' (pun intended :)).
I think those FTA tools that do support these gates
limit the number of arguments to 2 (e.g., graphically).
It would be unreasonable to require generality without a practical need.