On Wed, Dec 15, 2010 at 10:04 PM, Mathias Gaunard <mathias.gaunard@ens-lyon.org> wrote:
On 15/12/2010 13:34, Dean Michael Berris wrote:
This is just beautiful -- I think this is exactly what I need in cpp-netlib! Will this be submitted to Boost for review soon, because I really want to be able to deal with UTF-8 real soon now. :D
It could be submitted soon if I gave it a bit of love. If my talk about it gets accepted for boostcon 2011, I will definitely have it in the review queue several months before it starts.
Cool!
So, what are the features you'd like to implement so that us potential users can be the judge of whether it's feature-complete enough?
- I need to finish support for word, sentence and line boundaries
This doesn't sound like something I'd need, so I'm not going to wait for this.
- The ABI needs to be more clearly defined to guarantee backward and upward compatibility
I'm not too worried about ABI maintenance especially if I'm just going to write a header-only library that will require this, so that's not a deal breaker for me.
- The convert and segment subsystem must be clearly separated into its own library and namespace
Okay. This sounds like a good thing, but a migration path would be enough I think for people wanting to use the "current" version (assuming I can get it from the sandbox).
- The system must be made SIMD-ready
I don't see how this would be a requirement, but maybe it might be critical for some people who actually care that a text processing library would be SIMD ready.
- Simple case conversion should be added
I'd really like this, but not really too critical. I'm just more worried about encoding to UTF-8.
- General case folding (and maybe collation) should be added
This doesn't sound critical to me (well, I mostly need English and "webby" characters) but I guess this would be good.
Nothing among these is particularly difficult.
Cool, I'll look forward to giving it a whirl soon. :D Thanks Mathias! -- Dean Michael Berris deanberris.com