merge-rule evaluation order with string/char rules
Brought to you by:
jschrod
The non-regexp rules are evaluated strictly in order of
definition.
This might not be good since rules are specified in
several style files and one does not know what was in
advance, or what's new.
Wouldn't it be better to sort them by length of matched
text?
The evaluation order of regexp rules should be
documented. I assume, it's the DWIM implementation of
Gabor in ordrules.
Logged In: YES
user_id=70318
The issue with evaluation order of regexp rules has been
spun off to bug 1008035.