English version
Accueil     À propos     Téléchargement     Ressources     Contactez-nous    

Ce site est rarement mis à jour. Pour les informations les plus récentes, rendez-vous sur le nouveau site OCaml à l'adresse ocaml.org.

Browse thread
Class/prototype-based OO
[ Home ] [ Index: by date | by threads ]
[ Search: ]

[ Message by date: previous | next ] [ Message in thread: previous | next ] [ Thread: previous | next ]
Date: 2006-08-31 (07:32)
From: Jacques Garrigue <garrigue@m...>
Subject: Re: [Caml-list] Class/prototype-based OO
From: skaller <skaller@users.sourceforge.net>

> > Independently of downcasting, RTTI would also be needed for providing
> > more information in the debugger. But there seems not to be much
> > demand for that.
> I would note it is difficult to judge the utility of a missing
> feature :)
> Try to tell someone in the C++ community that C++ is severely 
> constrained because it doesn't have first class lexically
> scoped functions, variants, or pattern matching .. even
> if you explain what they are they'll just say "Oh, we can
> do that this way .. but don't have much call for it".

Here you have to read between lines :-)
I am a user of the debugger, and I also use objects at times, so I
have a personal interest in having better support for objects in the
debugger, through RTTI for instance. But this would be quite a bit of
work, so this is difficult to justify if I'm the only user. Hence the
above wording...
If you think of it, debugging contains all the difficulties of RTTI,
but without the justification for _not_ having it, that is, you clearly
want to break abstraction when debugging. So that to do things
properly, we would even want to now dynamic type information about
polymorphic types, which is even harder than for objects.

Jacques Garrigue