Type | Bug | Status | pending | Date | 7-Mar-2014 19:44 |
---|---|---|---|---|---|
Version | r3 master | Category | Parse | Submitted by | rebolek |
Platform | All | Severity | minor | Priority | high |
Summary | SET-WORD! after SET rule now doesn't work |
---|---|
Description | http://issue.cc/r3/2023 broke one rule that was valid in older code. See example: |
Example code |
Original behavior: >> parse [x][set val pos: word!] == true Current behavior: >> parse [x][set val pos: word!] == false |
Assigned to | n/a | Fixed in | - | Last Update | 14-Mar-2014 19:05 |
---|
Comments | |
---|---|
(0004352)
BrianH 7-Mar-2014 20:14 |
Yup, that's a bug in the implementation. I'll mark #2023 as a problem. |
(0004358)
abolka 8-Mar-2014 13:28 |
Thanks! Tests added to the core-tests suite. |
(0004359)
abolka 8-Mar-2014 20:18 |
Fix submitted: https://github.com/rebol/rebol/pull/208 |
Date | User | Field | Action | Change |
---|---|---|---|---|
14-Mar-2014 19:06 | BrianH | Comment : 0004352 | Modified | - |
14-Mar-2014 19:05 | BrianH | Status | Modified | reviewed => pending |
8-Mar-2014 20:18 | abolka | Comment : 0004359 | Added | - |
8-Mar-2014 13:28 | abolka | Comment : 0004358 | Added | - |
8-Mar-2014 05:10 | BrianH | Summary | Modified | SET-WORD! after SET rule now doesn't workT => SET-WORD! after SET rule now doesn't work |
8-Mar-2014 05:10 | BrianH | Description | Modified | - |
8-Mar-2014 05:10 | BrianH | Code | Modified | - |
8-Mar-2014 05:10 | BrianH | Status | Modified | submitted => reviewed |
8-Mar-2014 05:10 | BrianH | Priority | Modified | normal => high |
7-Mar-2014 20:14 | BrianH | Comment : 0004352 | Added | - |
7-Mar-2014 19:44 | rebolek | Ticket | Added | - |