January 31st, 2013, 12:00 AM
Design issue (loose vs strong coupling)
I have a function, but not a method, that is used to generate skinned meshes from it.
The object that is calling it will grasp a copy of this skinnedmesh from the out parameter,
which is not likely to be desired in today's software engineering practice.
But It is not very logical to encapsulate that function into that class since I want that generated skinned mesh
to be transient. Therefore, I need to pass more parameters to it, which increases the coupling.
Anyways, on a conceptual level, how can I improve this design?
Click Here to Expand Forum to Full Width