To view parent comment, click here.
To read all comments associated with this story, please click here.
Generally I'm not a fan of objects containing other objects and passing them as a single parameter. It makes the code less glance-able.
I haven't run into the situation where I need that many parameters and I would seriously question my design if I ever did. Methods in my opinion should have a clear purpose, and so many parameters would seem to indicate its trying to do too much at once.
I think the classic example is passing in a type of "Point", which contains x,y and z values. I agree if there is some massive class hierarchy it is probably being done wrong.
I think my overall point was that (as was yours) is that code shouldn't exist like that in the first place place and is not necessarily the fault of the language.
Edited 2013-01-25 09:05 UTC




Member since:
2009-08-18
But passing so many parameters is usually bad design code wise, I haven't needed to use it so I am not sure on it limitations on the types that can be parsed to it.