Hi Anders, Thanks for the link to Boost.Text! I think I missed it in the discussion I read. Yes, indeed I think we all share similar ideas. Other than difference in design, I think the concept is quite similar to Chad's Unicode string library, though I don't know whether you two have seen each other's code. Basically, my concept is also something like adding one more template parameter to your basic_text class to generalize string_type. Other than that, you have pretty much demonstrated my motivation to build such a class. One simple question to ask: May I know why is your class holding shared_ptr<basic_string<>> as the private member instead of simply basic_string<>? If I'm not wrong, basic_string<> is already a smart pointer to the underlying buffer and most implementation offers handy COW semantics. Or is there a need to wrap basic_string<> in shared_ptr<> because not all basic_string<> implementation is efficient? Thanks. On Fri, Mar 25, 2011 at 1:35 AM, Anders Dalvander <boost@dalvander.com> wrote:
On 20:59, Soares Chen wrote:
Hi everyone,
Thank you very much and I appreciate all your feedback! :)
I have talked privately with Chad Nelson and Mathias Gaunard over the past few days and they have give me a lot of useful suggestions. Based on the feedbacks and some study into Chad's Unicode library, Boost.Unicode and Boost.Filesystem, I have come out with some ideas on what kind of library should I build in this GSoC project.
Hi Soares,
Some of the issues you talk about are addressed or could be addressed with my Boost.Text library. Although I haven't worked on it since I posted it earlier this year.
http://www.dalvander.com/boost_text/
Please feel free to use any parts of it as you please. I'd be happy if it was of any use.
Regards, Anders Dalvander
-- WWFSMD? _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost