PARSE REMOVE COPY var rule doesn't copy

[Siskin-Bot]

Submitted by: Steeve

>> parse a: "12" [remove copy val skip] print [a val]
==2 none

So, the [remove] treats well the [skip], but discards the contents of [copy val].

Now, see:

>> parse a: "12" [remove [copy val skip]] print [a val]
== 2 1

The contents of [val] is preserved in that case, don't know why here, but not above...

>> parse a: "12" [remove copy val skip] reduce [a val]
== ["2" none]  ; should be ["2" "1"]

---

^{Imported from: CureCode [ Version: alpha 84 Type: Bug Platform: All Category: Parse Reproduce: Always Fixed-in:alpha 86 ]
Imported from: metaeducation#1244}

Comments:

Rebolbot commented on Sep 30, 2009:

Submitted by: BrianH

My guess is that the remove is being performed before the copy. To be useful, the remove should be performed after the copy.

---

Rebolbot commented on Oct 5, 2009:

Submitted by: Carl

The example code now produces the required result.

However, note that the application order of COPY, SET, RETURN, REMOVE, INSERT, and CHANGE is fixed (in that order.)

These words are flags, not functions. (They don't push onto a stack, they simply set bit flags for processing after the rule is matched.)

---

Rebolbot added Type.bug and Status.important on Jan 12, 2016

---