Re: Python syntax in Lisp and Scheme

From: Rayiner Hashem (gtg990h_at_mail.gatech.edu)
Date: 10/10/03 

Date: Fri, 10 Oct 2003 10:34:58 +0000

> Ahh, but overloading only works at compile time:
>
> void foo( SomeBaseObject* object );
> void foo( SomeDerivedObject* object );
>
> doesn't work if you're using a base class pointer for all your derived
> classes.
I think that the point was that the overload resolution rules can handle the
situation. Nothing in these rules prevents them from being applied to a
dynamically dispatched case.

Relevant Pages

  • Re: Function Overloading
    ... There can be some nasty "ambiguous overloading" bugs. ... It's usually some overhead at run-time (although this point may ... Overloading is fully resolved at compile time. ... overload resolution rules -- although it is never totally ...
    (comp.lang.c)
  • Re: Python syntax in Lisp and Scheme
    ... but overloading only works at compile time: ... > doesn't work if you're using a base class pointer for all your derived ... I think that the point was that the overload resolution rules can handle the ...
    (comp.lang.lisp)
  • Re: optional argument versus subroutine overloading
    ... Overloading is typically resolved at compile time. ... subroutine call at all. ... wouldn't repeat the test in the middle of a time critical loop inside of ...
    (comp.lang.fortran)
  • Re: polymorphism/boxing question
    ... there's no boxing involved in your examples. ... overloading is performed at compile time. ... doesn't hobble polymorphism, however, which is more about *overriding* ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: Equals() and inheritance
    ... The overloaded Equals() for object of type B is ... You're confusing overloading and overriding. ... but overloading is performed at compile time. ...
    (microsoft.public.dotnet.languages.csharp)