Type | Bug | Status | dismissed | Date | 5-Mar-2015 22:51 |
---|---|---|---|---|---|
Version | r3 master | Category | Unspecified | Submitted by | fork |
Platform | All | Severity | minor | Priority | normal |
Summary | Make ALL completely ignore UNSET! values |
---|---|
Description |
Currently, ALL *sort of* ignores unset values. Which is to say, an UNSET! will not cause the evaluation to fail and return #[none] >> all [10 print "Hello" 20] Hello == 20 However, if an unset happens at the end, that UNSET! value is returned: >> all [10 print "Hello"] Hello If an UNSET! is taken out of the consideration completely, that should return 10. Similarly, if all the evaluations are UNSET!, the result should be the same as an empty block (true). Today that is not the case: >> all [] == true >> all [print "Hello"] Hello |
Example code |
Assigned to | n/a | Fixed in | - | Last Update | 6-Mar-2015 01:24 |
---|
Date | User | Field | Action | Change |
---|---|---|---|---|
6-Mar-2015 01:24 | Fork | Status | Modified | submitted => dismissed |
6-Mar-2015 01:24 | Fork | Comment : 0004597 | Added | - |
5-Mar-2015 23:03 | Fork | Description | Modified | - |
5-Mar-2015 23:03 | Fork | Type | Modified | Wish => Bug |
5-Mar-2015 22:51 | Fork | Ticket | Added | - |