Browse thread
OO programming
[
Home
]
[ Index:
by date
|
by threads
]
[ Message by date: previous | next ] [ Message in thread: previous | next ] [ Thread: previous | next ]
[ Message by date: previous | next ] [ Message in thread: previous | next ] [ Thread: previous | next ]
| Date: | -- (:) |
| From: | Dirk Thierbach <dthierbach@g...> |
| Subject: | Re: [Caml-list] OO programming |
On Mon, Feb 25, 2008 at 10:49:49PM +0100, Tiphaine.Turpin wrote: > The few (2-3) programs of "not-toy" size that I did using objects > (either in Java or in Ocaml) both extensively used many linked > objects implementing lots of methods in a mutually recursive way, Then maybe one should look at one of those as a concrete example, and it might be possible to decouple those interdependencies. >>>> Much more annoying is that one also has to give types to arguments in >>>> methods that are unused (they are present make them compatible with >>>> another class, which uses them; >> Mutual recursive classes won't solve this problem at all. > Yes it does, I think (wether it's a good way of solving it is > debatable). If you declare the classes generating events together with > classes that handle them, I can't. First, they are not necessarily classes. Second, all this stuff is provided by the GUI framework, which I cannot change. - Dirk