«

On Jul 21, 2008, at 3:39 AM, aidy wrote:

> Hi,
>
> I am reading a book on Java OO.
>
> Could anyone tell me why Ruby does not include protected members nor
> explicit abstract classes?
>
> Thank You
>
> Aidy


as rubyists, we never protect our members.

a @ http://codeforpeople.com/
--
we can deny everything, except that we have the possibility of being
better. simply reflect on that.
h.h. the 14th dalai lama

>
> On Tue, 22 Jul 2008, Dean Wampler wrote:
>

>>
>> I prefer the ruby way;
>
> That's a bit of a conversation-stopper

Oh no problem, I'll teach him Ruby .
>
>> let my automated tests confirm that the required methods are present
>> when I include a module in another module, where the included module
>> expects the including module to respond to a set of methods. Also,
>> the tests document the behavior for the users!

That's exactly what I do in my *applications.
However, I really try to be defensive when developing libraries or frameworks.
David put it quite nicely, there are cases where I offer a service to
a user. If it fails with a method missing deep inside the call stack
the user just has to debug my framework or library to understand what
happened (well of course it should be in the docs LOL).
The least I want to tell him is:
Pally, look this thingy of yours you passed into foo does not look
like a bar, sure U know what UR doing?
Now of course she knows exactly what to do .

Again in general I agree, I will not check for protocols or methods in
my standard application, that is what tests (or microtests ) are for.


Cheers
Robert