home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!haven.umd.edu!darwin.sura.net!mips!pacbell.com!UB.com!igor!thor!rmartin
- From: rmartin@thor.Rational.COM (Bob Martin)
- Newsgroups: comp.lang.c++
- Subject: Re: Novice? question: Designing for multiple inheritance w/ templates
- Message-ID: <rmartin.712272453@thor>
- Date: 27 Jul 92 21:27:33 GMT
- References: <1992Jul9.144630.10863@clpd.kodak.com> <1992Jul20.152931.8037@ucc.su.OZ.AU> <1992Jul21.131054.20622@mole-end>
- Sender: news@Rational.COM
- Lines: 23
-
- mat@mole-end writes:
-
-
- |This is exactly what I was saying. The thing added by Virtual MI is added
- |not for the sake of what the class represents, but for the sake of the
- |class representation. It doesn't represent something in the problem
- |domain and won't appear on an object-occurrence or class-relationship
- |diagram. Instead it provides something that belongs to the solution domain,
- |to the properties of the programmatic object rather than the analysis
- |object.
-
- I don't think this is a hard and fast rule. It would not surprise me
- to find a class in the problem domain which must conform to more
- than one interface. But I think it is pretty rare. I agree with you,
- MI is more of tool in the solution domain, then an expressive
- component of the problem domain.
-
-
- --
- +---Robert C. Martin---+-RRR---CCC-M-----M-| R.C.M. Consulting |
- | rmartin@rational.com |-R--R-C----M-M-M-M-| C++/C/Unix Engineering |
- | (Uncle Bob.) |-RRR--C----M--M--M-| OOA/OOD/OOP Training |
- +----------------------+-R--R--CCC-M-----M-| Product Design & Devel. |
-