On Nov 11, 2008, at 1:37 PM, Charles Oliver Nutter wrote:

>> It will also make handling of the returned object much prettier.  
>> I'd much rather see
>> method(:foo).parameters.names.include? :some_param
>> than
>> method(:foo).parameters.any? { |param| param.include? :some_param  
>> if param.kind_of? Array }
>> or however it would be represented. Similarly, what expresses what  
>> you want the most; `parameters.takes_block?` or `! 
>> parameters.last.nil?`?
>
> Strongest argument I've seen for a real class. I'm more in favor of  
> that now.

Before this all grows to some large API, I was wondering: what actual  
value are we trying to generate here. "Reflecting on method  
parameters" is a technique, but what do we need to do with the result  
that needs all this complexity? (I'm not saying it isn't needed, I'm  
just having a hard time seeing what cold be needed that isn't answered  
with an array of strings.



Dave