Re: Performance tips when using regular expressions (regexps) in font-locking

[Stefan Monnier]

> I have enhanced my cc-mode with extra font-locking for assignments,
> function calls, numerical literals, operators and even format strings
> to the [sf]?printf-functions. The regular expressions describing these
> context are quite complicated and as a result my cc-mode is no longer
> as snappy as without my enhancement. Does any have any tips on how to
> write regular expressions when performance is crucial? For example
> should I use [:space:] instead of [ \t]? Should I post the coden
> aswell?

I believe inmost cases micro-optimization such as choosing between
[[:space:]] and [ \t] will make no noticeable difference.
But you should pay attention to * and + operators, especially when
nested or when adjacent and make sure that there is no redundancy: there
should ideally be only one way for the regexp to match a given piece
of text.

E.g. avoid [ab]*a*


        Stefan