From: Fabian Streitel <karottenreibe@...>
Date: 2009-09-01T16:59:01+09:00
Subject: Re: What is the ruby conventions to name private method?

--00504502ce40d3857d04727f85df
Content-Type: text/plain; charset=ISO-8859-1

> Fabian seems to have missed a point he made himself:
>
>
Alright, point taken, "subjective convention" wasn't well formulated. But I
remember
many many "4 spaces is better than 2 tabs" discussions (and the like),
all of which seemed very pointless to me, since in the end, everyone did
what he thought
was best anyways. It's like discussing the Zelda timeline -- you're never
gonna reach a
definite answer.


No. I _never_ do. I can't remember a single time in my 9 years of ruby that
> I've needed or even wanted private method visibility.
>

Well, I do. Maybe you're a better programmer than me and don't write stuff
that needs
it, but I sure do. And not using them would have either meant code
duplication or putting
functionality into public methods that wasn't meant to be publicly called.

Like you yourself said:

If you need to improve readability by separating sections of a method
> with empty lines, then it's a sure sign that you should have split
> that method!
>

And I agree!
But I don't want internal class functionality accessible as public methods,
because that
will expose the interal code to a public interface, which is definitely not
what I want.
So i make it private/protected. And what's the harm?
Or am I missing some better solution here?

Greetz!

--00504502ce40d3857d04727f85df--