I have spent time on this in Bergen -- almost the entire week -- on Windows problems. @theod is aware of the problems.
At this point the TTString rewrite is ready for somebody else to take over.
There are two branches:
windows-string-rewrite is based on std::vector internally
windows-string-rewrite2 is based on std::string internally
These branches have critical ruby script updates, other windows-related-fixes, and partial rewrites TTString.
My feeling at this time is that we should abandon the idea of wrapping an internal instance from the STL and write everything with the memory management etc. from scratch. However, I'll let the person who actually rewrites TTString make that determination.
I have spent time on this in Bergen -- almost the entire week -- on Windows problems. @theod is aware of the problems.
At this point the TTString rewrite is ready for somebody else to take over.
There are two branches:
These branches have critical ruby script updates, other windows-related-fixes, and partial rewrites TTString.
My feeling at this time is that we should abandon the idea of wrapping an internal instance from the STL and write everything with the memory management etc. from scratch. However, I'll let the person who actually rewrites TTString make that determination.