For those not reading ruby-dev, I just wanted to point to
a series of mails today. In [ruby-dev:33189], Akira Tanaka
pointed out a non-linear performance problem with
String#each_char.

It turned out that this iterator started at the start of the
string for each next character, very inefficient indeed. This
is now fixed. Some programs may run much faster now, for others,
it will not make a difference. It's a typical example of the fact
that the new String implementation still may need some tuning.

Any help (e.g. simple examples where performance is clearly non-
linear where it should be close to linear) is appreciated.

Regards,   Martin.


#-#-#  Martin J. Du"rst, Assoc. Professor, Aoyama Gakuin University
#-#-#  http://www.sw.it.aoyama.ac.jp       mailto:duerst / it.aoyama.ac.jp