|
-
November 9th, 2009, 10:54 AM
#1
How to apply a design pattern to a has-a but not a completely has-a case?
I'm not sure if this thread fits this forum, but it's a general C++ design question.
In my case, let's say, object A should have a object B, but B would use some methods exposed by A, so it's not a completely has-a relationship.
If I have B derive from class A, it would work, but strictly B is NOT an A. So, is there a design pattern apply to my case?
thx.
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|