From: George Ogata <g_ogata@...>
Date: 2004-04-02T08:29:27+09:00
Subject: Re: deciding between ruby and python

Ville Vainio <ville@spammers.com> writes:

>>>>>> "Hal" == Hal Fulton <hal9000@hypermetrics.com> writes:

> And hence, the sequence knows about strings. The Ruby approach is
> making a special case of strings, while the Python approach doesn't.
>
> I'm not saying this is a question of big importance - we have lots of
> people in Python camp who don't like ''.join() either. It just seems
> most sensible for me, even if it isn't obvious for newbies. I think
> it's a situation where Python errs on the side of pure OO instead of
> practicality.

It's not String-specific; it calls the elements' #to_s methods, and
joins the result.

I don't see how this makes it any more "un-OO" than #sort, e.g., which
requires the elements to be comparable (in fact, comparable _with each
other_), or do you have issues with that too?