home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!mcsun!corton!seti!nuri!ziane
- From: ziane@nuri.inria.fr (ziane mikal -)
- Newsgroups: comp.lang.c++
- Subject: Sigh. So, what is a proper class definition ?
- Message-ID: <4227@seti.UUCP>
- Date: 15 Sep 92 17:41:34 GMT
- References: <4210@seti.UUCP>
- Sender: news@seti.UUCP
- Organization: INRIA Rocquencourt,Le Chesnay, France.
- Lines: 35
-
- Since nobody replied to the article reproduced below I infer that
- posting it in another group might be better.
- Any idea ?
-
- Thanx in advance (Mikal.Ziane@inria.fr)
-
-
- ----------------------------
- Since nobody replied to my previous posting I'll rephrase differently.
-
- The main motivation is due to always increasing class public parts
- while my application is getting more developped.
-
- Is it normal to have a class interface increase constantly ?
- I find it very annoying because it becomes very hard to undersatnd
- the meaning of the class.
-
- I have the fealing that the interface should be defined once and be
- as stable as possible, but I always need more functionality.
- The pb is that this functionality could be put outside of the interface
- sometimes but it is convenient or efficient to use a public method
- rather than a non-member function.
-
-
- Also, it is not so easy to decide what must be part of the definition
- and what must not.
- For example if I want a class List with only const objects I have a problem
- to define what a list is. A list can be recursively defined in terms of
- a simpler one. Should I define a constructor for each "axiom" of such
- a definition ?
- For example "insert" would be forbidden, but how shall I define complex
- lists ?
-
- Mikal
- -----------------------------
-