Esmail
8/27/2007 12:05:00 AM
dblack@wobblini.net wrote:
> Hi --
>
> On Mon, 27 Aug 2007, Esmail wrote:
>
<..>
>> Comments? Please, I am not looking for an argument here.
>
> The original question was how to make it more succinct, not more
> elegant or transparent. As it happens, I don't think there's anything
> particularly unclean or unreadable about the code above, though I've
> pretty much given up on "readable" as a meaningful term.
:-)
> Another point is that while Ruby certain does (in my view) provide
> favorable conditions for writing nice-looking code, it's important not
> to be *too* skittish about the use of constructs that can't always be
> picked up at a glance. Some Ruby constructs are easier to read, and
> for different people, than others. It was never part of the Ruby
> contract, so to speak, that no one would have to make an effort to
> learn how to read Ruby.
Good points .. though in general I will favor "readability" (whatever
that exactly means to everyone) over "cleverness" .. after all people
end up reading/comprehending and possibly modifying the code, so it's
good to help them as much as possible. Of course, as you say, this
doesn't mean no effort should be made to know the language and its
idiomatic expressions.
Esmail