Re: procedural vs object oriented
- From: Jean-Pierre Rosen <rosen@xxxxxxxxx>
- Date: Thu, 27 Apr 2006 16:01:41 +0200
Dmitry A. Kazakov a écrit :
Well, no:Of course, you can assume that every dispatching call is equivalent to a case statement over all possibly redefined primitives. That works well for one level.
if Read (File) then
Foo;
else
Bar;
end if;
The uncertainty of a dispatching call is one of the context, exactly as in
the example above. Provided, that there is nothing uncertain in how
dispatching works or what potential targets do.
But if you consider that each called primitive may in turn redispatch internally, you end up with a combinatorial explosion. In theory, yes, the analysis can be performed. In practice, no.
--
---------------------------------------------------------
J-P. Rosen (rosen@xxxxxxxxx)
Visit Adalog's web site at http://www.adalog.fr
.
- Follow-Ups:
- Re: procedural vs object oriented
- From: Dmitry A. Kazakov
- Re: procedural vs object oriented
- References:
- procedural vs object oriented
- From: Ananth the Boss
- Re: procedural vs object oriented
- From: bh
- Re: procedural vs object oriented
- From: Ludovic Brenta
- Re: procedural vs object oriented
- From: Dmitry A. Kazakov
- Re: procedural vs object oriented
- From: Ludovic Brenta
- Re: procedural vs object oriented
- From: Dmitry A. Kazakov
- procedural vs object oriented
- Prev by Date: Re: procedural vs object oriented
- Next by Date: Re: Type safety, C++ and code generation
- Previous by thread: Re: procedural vs object oriented
- Next by thread: Re: procedural vs object oriented
- Index(es):
Relevant Pages
|