home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.lang.c++
- Path: sparky!uunet!utcsri!torn!nott!bnrgate!bcrka451!bcrki65!sjm
- From: sjm@bcrki65.bnr.ca (Stuart MacMartin)
- Subject: Re: Criticisms Wanted
- Message-ID: <1992Nov11.175117.15325@bcrka451.bnr.ca>
- Sender: 5E00 Corkstown News Server
- Organization: Bell-Northern Research Ltd., Ottawa, Canada
- References: <1992Nov8.170309.12301@cc.gatech.edu> <BxGu0p.D3o@slipknot.rain.com> <1992Nov11.170816.24497@cc.gatech.edu>
- Date: Wed, 11 Nov 1992 17:51:17 GMT
- Lines: 30
-
- In article <1992Nov11.170816.24497@cc.gatech.edu> brianm@cc.gatech.edu (Brian N. Miller) writes:
- >In article <BxGu0p.D3o@slipknot.rain.com> robert@slipknot.rain.com.UUCP (Robert Reed) writes:
- >>
- >>The argument goes that if you
- >>still have to examine the internal workings of component classes to determine
- >>how to best use them, then their value as components has been greatly
- >>diminished.
- >
- >Ok. So anybody have any ideas?
-
- Documentation, anyone?
- Obviously the C++ syntax for the class interface does not tell me anything about
- how to use the class correctly for a given situation. If I am a provider of a class,
- surely it is my responsibility to identify the needs of my clients (the users of
- the class) and to give them sufficient information about the class.
-
- The real question is *why* does the user have to look into the inner workings of
- the class? Surely not to discover the inner workings, but to discover behavioural
- characteristics of the class. Will these be clear from looking inside the class?
- Does the user enjoy poking his nose around where he doesn't belong?
-
- I don't think that C++ is self-documenting code. Usage notes should be provided
- where appropriate.
-
- Stuart
-
- --
- : Stuart MacMartin email: sjm@bnr.ca :
- : Bell-Northern Research phone: (613) 763-5625 :
- : PO Box 3511, Stn C, Ottawa, K1Y-4H7, CANADA Standard disclaimers apply. :
-