Gus writes:
> Loren Wilton wrote:
> >> rule work, but the ones with the "\|\\\|" (matching "|\|") all choke:
> >>
> >> "fro|\""|"{RET("__XM_Sft_Ms_Fp_L33T");}
> >>
> >> It produces the above output, instead of "fro|\|". Not sure what it's
> >> doing. Any solution other than commenting
It's consistently interpreting escaped backslashes (\\) as either \" or
\"", which screws re2c up because that creates an incorrect amount of "'s.
I even tried escaping it has hex "\x52" (or whatever the right number
was--don't have my ascii table handy anymore :).
Sounds like opening a Bugz
Loren Wilton wrote:
rule work, but the ones with the "\|\\\|" (matching "|\|") all choke:
"fro|\""|"{RET("__XM_Sft_Ms_Fp_L33T");}
It produces the above output, instead of "fro|\|". Not sure what it's
doing. Any solution other than commenting out the offending rules?
What version
rule work, but the ones with the "\|\\\|" (matching "|\|") all choke:
"fro|\""|"{RET("__XM_Sft_Ms_Fp_L33T");}
It produces the above output, instead of "fro|\|". Not sure what it's
doing. Any solution other than commenting out the offending rules?
What version of re2c? There repo
Gus wrote:
Sorry if this has come up at all, but I have a few rules that sa-compile
chokes on. Wondering if there's a way around it...
Here's an example.
Original rule:
/(?:fr(?:o|0|\(\))(?:n|\|\\\|)[EMAIL PROTECTED])/i
Sa-compile seems to interpret every branch of this, so we end up with
