Re: Workaround for (not-allowed) numbers in variable names?

[David Wright]

On Sun 07 Mar 2021 at 14:48:08 (+0000), Peter Toye wrote:
> The 2.22 documentation is obviously better here:
> 
> The name of a variable should not contain (ASCII) numbers, multiple 
> underscores, multiple dashes or space characters. All other characters 
> Unicode provides are allowed, for example Latin, Greek, Chinese or Cyrillic. 
> Non-adjacent single underscores and dashes are allowed, too. In other words, 
> variable names like HornIII or ???XII work.

Because Unicode is supported, one can avoid all these syntactic
complications by using any one or more of these number sets:

¹ superscripts
₂ subscripts
③ circled
⑷ parenthesised
⒌ bundled with a period
⓺ double circled

> Any combination of characters is allowed if the variable name is enclosed in 
> double quotation marks. In this case backslashes and double quotation marks 
> need to be escaped with backslashes (not that you actually should use them). 
> Examples: "foo bar", "a-b-c", "Horn 3". 

Cheers,
David.