On Fri, Mar 18, 2011 at 5:33 AM, Phil Endecott <spam_from_boost_dev@chezphil.org> wrote:
Hi Dean,
Dean Michael Berris wrote:
Hi everyone, I just wanted to give a heads up to say that I'm actually now trying to get the Boost.Chain idea a little more weight by defining the interface of the type -- as you might remember, "chain" was pretty much the immutable string. I wanted to point those interested over to the Git repository and project page over on Github (https://github.com/mikhailberis/chain) and either watch the repository or submit pull requests if you fancy filling in some of the blanks there.
I wonder, would it be a good idea to put together some sort of "string benchmark" suite? After all the previous discussion of string implementation styles, and the similar COW-or-not discussions in the XInt review, and considering the existing variations in string implementations between standard libraries, maybe it would be a good idea to try to quantify things?
+1
Perhaps this has already been done by someone?
If it has been done, I definitely would like to use it. :)
(Personally, although I use std::string a lot, it is almost never in an inner loop or other critical code.)
That's fine, I deal with lots of network I/O as part of the HTTP implementation in cpp-netlib and it would be really good if I can step away from std::string from the internals to support larger strings without having to induce too much fragmentation when concatenating strings. The intention is to have suitably efficient (not necessarily optimal) string representations for code that need to deal with both small and potentially huge strings. Maybe if others would like to put the benchmark code under a Boost Software License and be pulled in from the chain project as a pull request, that would very much be welcome. Thanks Phil! -- Dean Michael Berris http://about.me/deanberris