On 24/03/2007, at 11:52 AM, Guyren Howe wrote: > On Mar 23, 2007, at 8:48 PM, Guyren Howe wrote: > >> 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. > > Is there no-one else on this mailing list who uses any of the many > languages that have multiple return values who will jump in here and > confirm that, in fact, this turns out not to be a huge mis-feature in > those languages, that it works fine, that it does not *actually* > cause your hair to turn out or require you to sacrifice your first- > born?
Me. I haven't the time or patience to read all the posts but happened to hit this one. Yes, I frequently use multiple return values in Python. Yes, it works well in some circumstances, like getting the key and value back in one hit from a dictionary. In C++ I might use a lightweight structure but C++ has stack objects with optimisation and little or no memory hit, unlike REALbasic. However, in comparison to the vast number of things that RS have to do: a) bugfixes b) Cocoa framework c) more compiler optimisations d) IDE improvements that will help my productivity more I'm sorry to say I put this a long way down the list. _______________________________________________ Unsubscribe or switch delivery mode: <http://www.realsoftware.com/support/listmanager/> Search the archives: <http://support.realsoftware.com/listarchives/lists.html>
