Re: Imitation is the sincerest form of flattery

["Frank J. Lhota" <NOSPAM.lhota.adarose@verizon.net>]

"Dmitry A. Kazakov" <mailbox@dmitry-kazakov.de> wrote in message
news:b5qcnq$2bshmf$1@ID-77047.news.dfncis.de...
> Frank J. Lhota wrote:
>
> > I wish that we had the following functions defined in the Standard
> > package:
> >
> >     function Pred( X : Integer ) return Integer;
> >     function Max( X, Y : Integer ) return Integer;
> >     -- etc.
> >
> > This would allow the programmer to re-define any of these attributes for
> > types derived from Integer (or other predefined types).
>
> True, but it is a very long way to go. For example, to have 'Max
> dispatching, you would immediately need true multiple dispatch - it has
two
> parameters!

AFAIK (and my testing seems to confirm this) if we have the function

     function Max( X, Y : An_Integer_Type ) return An_Integer_Type;

defined in the same package as An_Integer_Type, and if we derive a type
New_Integer from An_Integer_Type, i.e.

    type New_Integer is new An_Integer_Type;

then New_Integer inherits Max from An_Integer_Type, i.e. there is an
implicit function

     function Max( X, Y : New_Integer ) return New_Integer;

that the programmer can either call or replace with his own version.

Multiple dispatching would only be an issue if we wanted to generate a
version of Max that compares and / or returns different integer types. By
the very nature of the Max function, we are unlikely to even want to do
that. This is not to dismiss the utility of multiple dispatching, but
unfortunately most OOPL's avoid it because of efficiency concerns.