http://www.tbray.org/ongoing/When/200x/2003/05/17/Yooster
It's a Ustr, a UTF-8-based unicode string intended (roughly) to be a fully-unicode-supporting replacement for Java's UTF-16 string. It implements many of the familiar C functions like strcpy, strlen, strstr, and so on. It may not be something we'll use, but I still believe that there's performance to be gained by reducing the complexity/overhead of heavy-use classes like RubyString. A RubyString based on a UTF-8 byte array (with support for full unicode) could be more efficient than our current use of String and StringBuffer (which are UTF16, therefore wasteful; converted to/from UTF8 for *everything* in Ruby, therefore less-than-efficient). Of course, String and StringBuffer have been endlessly optimized over the years, and we'd lose the ability to pass RubyString's value quickly and easily to code that expects String...but it could be worth investigating.
I recommended he throw it on SourceForge (or something)...so we'll see.
--
Charles Oliver Nutter @ headius.blogspot.com
JRuby Developer @ jruby.sourceforge.net
Application Architect @ www.ventera.com
_______________________________________________ Jruby-devel mailing list Jruby-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jruby-devel
