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
multiple regex's in the scanner#.re files. Some branches of the above
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?
Even escaping the ascii code for a backslash produces the above output.
Weird...
This doesn't fix the misinterpretation, but for the time being I've
replaced re2c with a wrapper script that first runs some sed
substitutions to fix the scanner#.re files, then runs re2c.
<shrug>
--
Gus
