Robert Klemme wrote:
>> I can't remember whether there are any methods that protest
>>if you give an argument and a block....  I have a memory that there
>>are one or two, but I'm not sure what they are.
> 
> Well, what implication would that have?  Do you mean to say it's not
> common in Ruby to have methods that either accept a block or an argument?

I think it's common to accept a block or an arg, but it raises the
question of what to do when *both* are given:

   1. raise an exception
   2. do something meaningful

And I'm not sure whether most core methods do (1) or (2).


Hal