TRANSCODE/error of an invalid serialized constructor triggers the error it should insert

[Siskin-Bot]

Submitted by: BrianH

When you use the /error option of TRANSCODE it should not trigger syntax errors, it should insert the error object in the return value untriggered. However, it triggers the error instead, as if the /error option wasn't specified.

; Properly formed but semantically invalid constructor
>> transcode/error to-binary "#[block! 1]"
** Syntax error: invalid constructor: [block! 1]
** Where: transcode
** Near: transcode/error to-binary "#[block! 1]"

; The above should return something like this instead
== [make error! [
        code: 205
        type: 'Syntax
        id: 'malconstruct
        arg1: [block! 1]
        arg2: none
        arg3: none
        near: "(line 1) #[block! 1]"
        where: [transcode]
    ] #{}]

; Bad syntax (note the badly formed error)
>> transcode/error to-binary "#["
** Syntax error: invalid constructor: make error! [
    code: 201
    type: 'Syntax
    id: 'missing
    arg1: "end-of-script"
    arg2: "]"
    arg3: none
    near: "(line 1) #["
    where: [transcode]
]
** Where: transcode
** Near: transcode/error to-binary "#["

; This is what should happen in the above case
== [make error! [
        code: 201
        type: 'Syntax
        id: 'missing
        arg1: "end-of-script"
        arg2: "]"
        arg3: none
        near: "(line 1) #["
        where: [transcode]
    ] #{}]

---

^{Imported from: CureCode [ Version: alpha 110 Type: Bug Platform: All Category: Native Reproduce: Always Fixed-in:none ]
Imported from: metaeducation#1857}

Comments:

---

Rebolbot mentioned this issue on Jan 12, 2016:
wrong error on load "1abcde"

---

Rebolbot mentioned this issue on Jan 22, 2016:
[Epic] Holes in our evaluation model

---

Rebolbot added the Type.bug on Jan 12, 2016

---