| Type | Bug | Status | submitted | Date | 19-Nov-2010 22:37 |
|---|---|---|---|---|---|
| Version | alpha 110 | Category | Native | Submitted by | Sunanda |
| Platform | All | Severity | minor | Priority | normal |
| Summary | REDUCE/ONLY emits UNSET for undefined word |
|---|---|
| Description |
REDUCE generates an error:
reduce [1 no-such-word 2] ** Script error: no-such-word has no value ** Where: reduce ** Near: reduce [1 no-such-word 2] While REDUCE/ONLY generates an UNSET! reduce/only [1 no-such-word 2] [] == [1 unset! 2] R2 generates an error in each case. So, at the least, this is an undocumented change in behaviour. |
| Example code |
| Assigned to | n/a | Fixed in | - | Last Update | 5-Mar-2014 09:41 |
|---|
| Comments | |
|---|---|
|
(0004314)
BrianH 5-Mar-2014 09:41 |
Shall we document this or fix it? We need to do the better behavior, whether or not it's Rebol 2 compatible. Does anyone value the new behavior? That error seems pretty useful, especially since the /only option seems unrelated to unset words. We need a choice here. |
| Date | User | Field | Action | Change |
|---|---|---|---|---|
| 5-Mar-2014 09:41 | BrianH | Comment : 0004314 | Added | - |
| 19-Nov-2010 22:37 | sunanda | Ticket | Added | - |