Re: Design rationale of CoreHelper

Thank Linus and Blob for the reply. So I guess CoreHelperMDRImpl.java is
another Facade to the subsystem of MDR, besides FacadeMDRImpl. That's a
common role for large classes.

PS: The mailing list still has some problems. I can't see this thread in
the topic list, and had to reach this through Google

*Regards,*
*Zhongpeng Lin*



On Sun, Apr 22, 2012 at 11:54 AM, Zhongpeng Lin <[email protected]> wrote:

> I found most of methods declared in Corehelper are procedural style
> instead of OO style: object of an operations is passed as a parameter
> of the operation, as oppose to calling operations on the object. By
> putting all the "utility methods" in this interface, it makes its
> implementing classes god classes. Also, it seems that CoreHelper was
> not introduced accidentally, but was designed intentionally. What is
> the design rationale of this class instead of distributing the
> function among classes? Did such god classes do any harm to the
> development?
>
> I am a PhD student doing research on the evolution of large source
> code files. Any inspiration would be appreciated!
>
> Regards,
> Zhongpeng Lin
>

------------------------------------------------------
http://argouml.tigris.org/ds/viewMessage.do?dsForumId=450&dsMessageId=2957137

To unsubscribe from this discussion, e-mail: [[email protected]].
To be allowed to post to the list contact the mailing list moderator, email: [[email protected]]