Hello,
John Chambers:
> Simon Wascher writes:
> | I would like to add:
> | [1+3
> | and
> | [1&3
(...)
> My current implementation has
> "-,.0123456789" as the legal chars; making it "-,.+&0123456789" is a
> one-line change. (In an earlier discussion, someone also suggested
> including "x", but I don't recall what that meant.)
By the way: '[1+3' and '[13' (thirteen) should be legal but '[13+' ('+'
being the last char, not followed by a number) cannot be legal: its
ambigous with the +CEG+ chord notation. Similar case is '[n-' and '[n.'
[nx .
This leads to a list for all chars that *cannot* be part of the
'<numeral>' ending syntax:
1) all letters and obviously: '%', '\'
2) following chars cannot be the *last* char of a ending string (exept
in the proposed "<text>" case):
'+', '-', '.', '(', '[', '~', '<space>', '_', '^', '=', '{',
In fact the last char in the <numeral> ending syntax must be a number.
All other chars would be recognized as part of the following abc text.
More general one could say:
$ a <numeral> ending begins with a '[' sign followed
$ by any number or by a string of any chars exept letters
$ (and '%' or '\'). The string must end with a number.
I know this is fairly liberal, but thats my weltanschauung.
Simon Wascher - Vienna, Austria
http://members.chello.at/simon.wascher/
To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html