MAKE ERROR! does not process THROWN values as THROWN

[Siskin-Bot]

Submitted by: fork

Similar to #2243. MAKE ERROR! evaluates the block it is passed like MAKE OBJECT! does. But if a THROW-style operation happens (including CONTINUE, BREAK, RETURN, etc.) then rather than handling it, it will process the THROWN()

>> make error! [type: 'Access arg1: 10 + 20 id: 'Protocol]      
** Access error: protocol error: 30

>> make error! [type: 'Access arg1: throw 10 + 20 id: 'Protocol]              
** Internal error: error object or fields were not valid   ;-- expect "unhandled throw"

---

^{Imported from: CureCode [ Version: r3 master Type: Bug Platform: All Category: Unspecified Reproduce: Always Fixed-in:none ]
Imported from: metaeducation#2244}

Comments:

---

Rebolbot added the Type.bug on Jan 12, 2016

---

Ladislav commented on Feb 6, 2016:

For the terminology, see also http://www.rebol.com/r3/notes/errors.html

---