>> Thanks Robert - do you understand why Ruby allows the "send :x" method to
>> work here, but not the ".x" out of curiosity?  Does this make sense to
>> people it should do this?

The whole point of the private/protected method deal is to prevent what 
you are trying to do :) Ruby, having lots of metaprogramming 
capabilities, lets you get around this "if you really know what you are 
doing" -- as you can see, it's a bit more of a pain then just the 
standard way of calling a method. It's to help keep you honest.

-- 
Posted via http://www.ruby-forum.com/.