On Mar 23, 2007, at 7:23 PM, Arnaud Nicolet wrote: > In my opinion, this makes things less clear. Also, even if you hate > ByRefs (that's also my case), there are "plenty" of other ways to > return a value, so why bother making another (confusing) way?
Because it's absurd overkill to define a new class as a way of holding multiple values, when all that's going on is that you need to return multiple values from some computation. I love OOP. But often, it's just overkill. When *all* that's going on is that I'm performing some computation that generates multiple values, I would like to just be able to return those multiple values. Why should returning a single value be easy but multiple values be a pain in the proverbial? I don't see anything special about returning one value. _______________________________________________ Unsubscribe or switch delivery mode: <http://www.realsoftware.com/support/listmanager/> Search the archives: <http://support.realsoftware.com/listarchives/lists.html>
