Anyhow, here's the thinking:
- Round out all the currently-missing std::basic_string equivalency methods, so that it can act as a full functional replacement
- Define its purpose. This is something that has confused STLSoft users over the years.
- Provide compile-time selection of its nature, facilitating user-selected customisations of its implementation
- It has a documented footprint, equivalent to a single char*, which is consistent across platforms/architectures/operating systems, allowing, for example, a user to pass a std::vector<stlsoft::simple_string> to a function taking an array of C-style strings
- It is, in some circumstances, more efficient than std::basic_string. Please note that superior efficiency is not a main design feature of the component, nor is it claimed in any general sense.
Post a Comment