Re: Performance implications of GRegex structure

Il giorno sab, 17/03/2007 alle 10.07 -0400, Matthias Clasen ha scritto:
> Btw, one thing we might want to consider doing (regardless if we go
> with separate pattern and matcher objects) is to make the pattern
> optimization an optional part of the constructor rather than a
> separate
> function. That will ensure that the pattern is truly immutable after
> construction. 

I prefer to keep it a separate function, what are the advantages of
having a truly immutable GRegex? Note that the _optimize function is
already thread-safe.

Marco Barisione

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]