[ragel-users] fnext followed by fbreak

[Adrian Thurston]

Hmmm, yes this needs to be fixed for sure.

Andrei Polushin wrote:
> For actions that involve both fnext and fbreak, I would suggest
> generating {cs = ...} in the beginning of the action, and omit
> that assignnment in the code generated by fbreak.

That seems like a good solution. Also, I think it's already half done in
-G2. When an action contains fnext there need to be a jump back into the
processing loop via a switch so CS is set just before the action.

-Adrian