RE: [Rails-devel] Interfaces in method signatures

[Brett <wak...@ea...>]

On Mon, 2005-04-18 at 09:17 +0100, Stewart Thain wrote:
> Brett,
> 
> In my opinion, this change is a backwards step. The main purpose for using 
> interfaces for all argument and return types is to allow objects of new 
> classes that implement the interface to passed in to existing methods.
> 
> To take your example of java.util.List. If you examine all of its methods, 
> *every* parameter and return type (with the exception of Object) is an 
> interface. Many of the arguments are Collection which is the parent 
> interface for List. Object of course can be anything anyway! :-)
> 
> To give you another example, take a look at the Collections utility class 
> (java.util.Collections), many of the methods take or return List, and again 
> with the exeception of Object, all of the myriad of arguments and return 
> types are interfaces.
> 
> regards
> 
> Stewart


Hmmmm...  you're right.

I had my thinking all backwards. I'll undo this change.


---Brett. 

You want to know why I kept getting promoted? Because my mouth knows
more than my brain. -- W.G.