knowledge-database (beta)

Current group: comp.object

Re: Static vs dynamic

Re: Static vs dynamic  
Isaac Gouy
 Re: Static vs dynamic  
Thomas G. Marshall
 Re: Static vs dynamic  
Thomas Gagne
 Re: Static vs dynamic  
Thomas G. Marshall
From:Isaac Gouy
Subject:Re: Static vs dynamic
Date:22 Jan 2005 16:14:46 -0800
> And that's considered "overloading"? It's not the overloading I
understand.

Does it agree with the definition of overloading you provided?
What do you understand by overloading that contradicts this usage?
Could it be that overloading is used to mean different things in
different contexts - it's overloaded ;-)
From:Thomas G. Marshall
Subject:Re: Static vs dynamic
Date:Sun, 23 Jan 2005 00:43:51 GMT
Isaac Gouy coughed up:
>> And that's considered "overloading"? It's not the overloading I
>> understand.
>
> Does it agree with the definition of overloading you provided?
> What do you understand by overloading that contradicts this usage?
> Could it be that overloading is used to mean different things in
> different contexts - it's overloaded ;-)

Oh jeez. lol.

No, the trouble I have with this is that in my example there was nothing
technically overloaded. Each class has its own method. They are not
overloaded, because they are not two methods of the same name within the
same class. They are just two separate classes that each have the same
method.

I suppose what I'm to learn from all this is that the mere fact that they
were used in a polymorphic manner necessitates that the two methods be
referred to as overloading each other. Somehow that just make me cringe.

--
Forgetthesong,I'dratherhavethefrontallobotomy...
From:Thomas Gagne
Subject:Re: Static vs dynamic
Date:Sun, 23 Jan 2005 10:54:18 -0500
The most memorable thing I've ready about overloading came from a C++ text,
describing how a class can define different methods for the same selector
based on the argument type.

print(int)
print(long)
print(char *)

are examples of overloading print(). Same method, different operations
switched by the argument type.

Operator overloading allows programmers to do a similar thing for
operators--defining different methods based on the operands.

Perhaps there are other definitions.

Isaac Gouy wrote:
>>And that's considered "overloading"? It's not the overloading I
>
> understand.
>
> Does it agree with the definition of overloading you provided?
> What do you understand by overloading that contradicts this usage?
> Could it be that overloading is used to mean different things in
> different contexts - it's overloaded ;-)
>
From:Thomas G. Marshall
Subject:Re: Static vs dynamic
Date:Mon, 24 Jan 2005 04:15:49 GMT

And inheritance-less polymorphism, like my original example, is which of the
polymorphisms I listed?



Thomas Gagne coughed up:
> The most memorable thing I've ready about overloading came from a C++
> text, describing how a class can define different methods for the
> same selector based on the argument type.
>
> print(int)
> print(long)
> print(char *)
>
> are examples of overloading print(). Same method, different
> operations switched by the argument type.
>
> Operator overloading allows programmers to do a similar thing for
> operators--defining different methods based on the operands.
>
> Perhaps there are other definitions.
>
> Isaac Gouy wrote:
>>> And that's considered "overloading"? It's not the overloading I
>>
>> understand.
>>
>> Does it agree with the definition of overloading you provided?
>> What do you understand by overloading that contradicts this usage?
>> Could it be that overloading is used to mean different things in
>> different contexts - it's overloaded ;-)



--
Whyowhydidn'tsunmakejavarequireanuppercaselettertostartclassnames....
   

Copyright © 2006 knowledge-database   -   All rights reserved