From: Erik Wien (wien_at_[hidden])
Date: 2004-10-21 19:45:54
"Ben Hutchings" <ben.hutchings_at_[hidden]> wrote in message
>> You are quite correct... It is slow. And that is why I am hesitant to
>> make decomposition something that will happen every time you assign
>> something to a string.
>> What this really boils down to, is what kind of usage pattern is the most
>> common? The library should be written to provide the best performance on
>> the operations most people do.
> How about this:
> - when initialising or assigning to a string, you can opt to normalise one
> way or the other, or not at all
> - normalised strings are flagged as such
> - normalisation on comparison can be skipped if both strings are flagged
> as being normalised the same way
> - normalisation on assignment can be skipped if the right-hand side is
> flagged as being normalised appropriately
That is not a bad idea... I think... ;) Providing a "normalization scheme"
as a setting in the string would be possible. I'll take that into
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk