Timeline for Simplify assumes Boolean 1 and 0 in logical expressions
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 9, 2013 at 22:49 | vote | accept | István Zachar | ||
| Feb 17, 2013 at 0:26 | comment | added | Szabolcs |
Sounds like the final outcome may not be intentional, just a side effect of how BooleanFunction works. @István Perhaps it worth letting support know about it in case it wasn't intentional. This sort of undocumented behaviour is not what one would hope to bump into.
|
|
| Feb 16, 2013 at 22:57 | comment | added | Jens |
@IstvánZachar But FullSimplify[Not[0]] does return True -- "fortunately." Maybe better use FullSimplify for more consistency.
|
|
| Feb 16, 2013 at 22:21 | comment | added | Simon Woods |
@IstvánZachar, looking at the Trace output, it seems that Not[0] doesn't get converted to a BooleanFunction. With the And[1,2] example there were heaps of calls to functions in System`BooleanDump and DiscreteMath`DecisionDiagram contexts, causing the conversion I mentioned. There was none of that for Not[0]. I agree this is scary, it makes for very inconsistent behaviour.
|
|
| Feb 16, 2013 at 22:01 | comment | added | István Zachar |
Wow. This is still scary. But then why does it not return True for Simplify[Not[0]]?
|
|
| Feb 16, 2013 at 21:22 | history | answered | Simon Woods | CC BY-SA 3.0 |