Why I found hard to get Internals Vs Peers definition
103 views
Skip to first unread message
Luca Minudel
unread,
Oct 28, 2012, 10:48:33 AM10/28/12
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to growing-object-o...@googlegroups.com
Hi,
here follow the assumptions that make it hard for me to get the definition of Internals and Peers as in the GOOS book and map these concepts to those I was using before.
1) As I understood Internals and Peers describe characteristics of an object as it inherently is and so how it should be implemented/coded. Instead I was thinking about how the object actually is in the code (that time to time it can happens to be legacy code or just bad code). So for examples it is common in legacy code to see Peers like Dependencies/Services that are instantiated in the object constructors like if they were Internals.
2) The peers stereotype 'Dependencies' in UML or general OO have a meaning that is different from one defined in the GOOD. This caused a misunderstanding.
HTH, Luca
Steve Freeman
unread,
Oct 29, 2012, 4:29:00 AM10/29/12
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to growing-object-o...@googlegroups.com
Thanks. Not enough people step back from the code they have in their hand and think about what they actually want.