Sebastien Martel <smartel@real.com> writes:
Hello boosters,
Thank you for looking over the comments I posted.
I completely forgot to mention one important thing boost.tokenizer 1.32 introduced that broke us when we moved from boost 1.31 :
Here is my post on the matter on boost-users
Essentially, the assign optimization (nice gains, thank you) adds requirements on the container type. We have a custom string classes that does not support it, but has a += member.
So any use of tokenizer on these fails to compile. I sadly had to revert back to 1.31 behavior until this gets resolved.
Thanks, -seb
( please cc me when replying, I do not follow boost@list ) --
You are welcome for the speed up. I thought the only additional constraint was that the container needed a constructor that took two iterators --- is there a reason you can't add such a constructor to your custom string class? Or is there an additional constraint I missed? Thanks, Robert