SECURE error message is unclear with incorrectly formatted input block

[Siskin-Bot]

Submitted by: henrikmk

>> secure [debug]
** Script error: datatype assertion failed for: pol
** Where: assert foreach secure
** Near: assert/type [target [word! file! url!] pol [block! word! int...

The correct input is secure [debug allow], but the error doesn't show this.

---

^{Imported from: CureCode [ Version: alpha 86 Type: Bug Platform: All Category: Error Handling Reproduce: Always Fixed-in:alpha 87 ]
Imported from: metaeducation#1255}

Comments:

Rebolbot commented on Oct 6, 2009:

Submitted by: Carl

There's not a perfect solution here, because the error message cannot include all possibilities. However, there is now a HELP option that will summarize the arguments and tell you where to get more info.

Online R3 Docs updated to reflect these changes.

---

Rebolbot added the Type.bug on Jan 12, 2016

---

[Oldes]

@henrikmk now it is:

>> secure [debug]
** access error: invalid debug security policy: none

>> secure [debug 2]
** access error: invalid debug security policy: 2

>> secure [debug allow]
>>