refinements starting with special characters are not correctly scanned

[Siskin-Bot]

Submitted by: meijeru

some words like the ones for operators are not always correctly recognized in refinement context, see code below

>> type? '+
== word!
>> to-refinement '+
== /+
>> type? /+
** Script error: + is missing its value2 argument
>> type? /!
== refinement! ; this one works, and still it is an operator (but a unary one, admittedly)

---

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

Comments:

Rebolbot commented on Jun 28, 2009:

Submitted by: Carl

Interesting bug. The problem is with special chars of the lexicon (like +-,.#%).

---

Rebolbot commented on Jul 14, 2009:

Submitted by: BrianH

Note this code:

>> [/+]
== [/ +]

TRANSCODE and TO-BLOCK recognize "/+" as being 2 words, not one refinement.

---

Rebolbot commented on Feb 17, 2011:

Submitted by: BrianH

See #1478 for < and >, #1856 for +, - and . characters.

---

Rebolbot mentioned this issue on Jan 12, 2016:
Words starting with +, - or . won't load in refinement form

---

Rebolbot added the Type.bug on Jan 12, 2016

---

[hostilefork]

Resolved as part of the commitment to the definition of legal "arrow words" (words including > or <).

metaeducation/ren-c@5a617b8