Re: Why no Ada.Wide_Directories?

["Yannick Duchêne (Hibou57)" <yannick_duchene@yahoo.fr>]

Le Thu, 27 Oct 2011 21:39:31 +0200, Robert A Duff
<bobduff@shell01.theworld.com> a écrit:
> In Ada, you can tell whether a procedure is dispatching at compile time
> of the declaration of that procedure.  And you can tell whether a given
> call is dispatching at compile time of that call.  No whole-program
> analysis needed.
If a call is not dispatching, it may be anything you want, this will be  
the same: a deterministic call. If you want classes, this is for  
dispatching call I suppose (*), if you do not expect to use dispatching  
calls, you may not need classes. Finally, I suppose if one want classes,  
that means he/she want dispatching calls. If someone want dispatching call  
on some high level custom types, that's OK; if someone wants dispatching  
calls on general purpose and basic type like Boolean, that's not OK, this  
cost too much, unless optimized.

To know when a call is dispatching or static, does not make dispatching  
calls less costly. If you want dispatching call to cost not too much, you  
have to optimize these calls, which requires the mentioned global  
analysis. If you do not think about dispatching calls, then you may not  
need classes.

Or else, what kind of classes was this all about ?

I may just have misunderstood the topic, I keep this in mind too.

(*) Not necessarily, but I feel this is really how things typically goes.

-- 
“Syntactic sugar causes cancer of the semi-colons.”  [Epigrams on
Programming — Alan J. — P. Yale University]
“Structured Programming supports the law of the excluded muddle.” [Idem]
Java: Write once, Never revisit