| Type | Bug | Status | dismissed | Date | 16-Jul-2011 01:29 |
|---|---|---|---|---|---|
| Version | alpha 112 | Category | Parse | Submitted by | GHigley |
| Platform | All | Severity | not a bug | Priority | low |
| Summary | Using COPY while parsing a block gives a block |
|---|---|
| Description |
When parsing a block, words set using COPY always contain the matched value within a block, while words set using SET do not. Perhaps this is not a bug, and it's a new behavior of which I was not aware. If so, why? |
| Example code |
>> parse [foo] [copy word 'foo (probe word)] == [foo] ; Why?! ; But SET gives the expected result >> parse [foo] [set word 'foo (probe word)] == foo |
| Assigned to | n/a | Fixed in | - | Last Update | 17-Jul-2011 18:14 |
|---|
| Comments | |
|---|---|
|
(0003187)
henrikmk 16-Jul-2011 11:44 |
Not a bug, otherwise you could not make sequences like this:
>> parse [boo hoo foo] [copy word to 'foo (probe word)] [boo hoo] which is quite different from: >> parse [boo hoo foo] [set word to 'foo (probe word)] boo R2 does the same. |
|
(0003188)
BrianH 16-Jul-2011 19:37 |
Yes, this is part of the design. If SET and COPY worked the same then we wouldn't need two operations, we could just have one. |
|
(0003189)
GHigley 17-Jul-2011 18:14 |
It's baffling to me that I've written several pretty complex REBOL dialects in R2 and never noticed this. |
| Date | User | Field | Action | Change |
|---|---|---|---|---|
| 17-Jul-2011 18:14 | GHigley | Comment : 0003189 | Added | - |
| 16-Jul-2011 19:37 | BrianH | Comment : 0003188 | Added | - |
| 16-Jul-2011 19:35 | BrianH | Description | Modified | - |
| 16-Jul-2011 19:35 | BrianH | Code | Modified | - |
| 16-Jul-2011 19:35 | BrianH | Severity | Modified | minor => not a bug |
| 16-Jul-2011 19:35 | BrianH | Status | Modified | submitted => dismissed |
| 16-Jul-2011 11:45 | henrikmk | Comment : 0003187 | Modified | - |
| 16-Jul-2011 11:44 | henrikmk | Comment : 0003187 | Added | - |
| 16-Jul-2011 01:29 | GHigley | Ticket | Added | - |