This is elegant to me. I think it can be put to work, but am not sure.
for_construct :
TOKEN_FOR optional_whitespace
identifier TOKEN_EQ number optional_whitespace
TOKEN_TO optional_whitespace
number
{
/* nodes with values at indexes $3, $5, $9 */
}
> On 6 Jul 2020, at 14:00, Maury Markowitz <[email protected]> wrote:
>
>> On Jul 4, 2020, at 6:46 AM, Christian Schoenebeck
>> <[email protected]> wrote:
>> The only thing that people are missing once in a while on scanner side is
>> unicode support
>
> I am missing the capability to support grammars with optional spaces between
> elements. In BASIC:
>
> FORI=1TO5
>
> is equivalent to:
>
> FOR I=1 TO 5
>
> I have yet to see an elegant way to model this in Flex. This topic comes up
> time to time here, so I don't think Unicode is the "only" thing.
