Re: Dispatch on the result still does not work?

["Dmitry A. Kazakov" <mailbox@dmitry-kazakov.de>]

On Sun, 12 Jul 2009 17:05:06 +0100, Chris Moore wrote:

> Dmitry A. Kazakov wrote:
>> On Sun, 12 Jul 2009 11:40:27 +0100, Chris Moore wrote:
> 
> <snip>
> 
>>> But the results type is T'Class.  It is not S.
>> 
>> Exactly. To be of T'Class is a prerequisite for dispatch.
>> 
>>> The original object to
>>> which X refers is of type S.
>> 
>> Therefore it could dispatch using S'Tag.
> 
> Only if you use X.Value.

Why shouldn't it? Consider:

   X : String := "abc";
begin
   X := ...;

You have to use the value of X here in order to know the constraint checked
in the assignment.

Your premise that there is no or cannot be any interaction between the left
and right hand sides of the assignment is wrong. In fact, in many cases it
is highly desirable to have an access to non-finalized LHS in assignment,
especially when dealing with memory-managed objects.

>>> But this is destroyed prior to the
>>> assignment of the value returned by Value.
>> 
>> This is an implementation detail.
> 
> This is how assignment works no matter what the language!

Strictly speaking it does not. An assignment cannot destroy anything before
assignment, i.e. itself. Destruction happens (if any) within the
assignment. Nothing tells at which point it has to be done.

-- 
Regards,
Dmitry A. Kazakov
http://www.dmitry-kazakov.de