Methods overriding and overloading?

The return type of a function is not part of its signature, thus it can't be overloaded.

This by definition of the language. – Thomas Matthews Dec 18 '09 at 17:55.

No, you cannot do that. What you can do in an overriden method is to return a pointer/reference to a type which is a descendant of the type returned by parent's method. Example: struct VA {} struct VB : struct VA {} class A { public: virtual VA * get(); } class B { public: virtual VB * get(); }.

If you remove virtual from Foo in your first example it will work and call Base::Foo.

See this previously asked question Puzzle: Overload a C++ function according to the return value.

Overloading with only change in the return value is not possible. Consider this: Base->Foo(); called without any return value assigning then compiler cannot deduce which method to invoke. Virtual keyword is used for creating VTable and thereby proving dynamic polymorphism.It has no impact on overloading methods.

The return value is not part of the signature, unfortunetly, so no.

As far as overriding is concern it is pertaining to class hirearchy and it possible to achieve runtime polymorhism. Class Abstract { public : virtual Abstract* Clone() const = 0; }; class Concrete1 : public Abstract { public : Concrete1* Clone() const { return new Concrete1(*this); } }; class Concrete2 : public Abstract { public : Concrete2* Clone() const { return new Concrete2(*this); } }; Overloading across scopes is not possible as per C++ standard.

No, there are some similar thing you can do however e.g. Templatize the return value (possibly with specializations) and specify the template type when calling e.g. Template T Foo() { return 0; } template double Foo() { return 3.14; } int I = Foo(); // 0 double d = Foo(); //3.14.

Actaully you may have to make them functors to do this properly – jk. Dec 18 '09 at 12:22.

You'll get a "overloaded method only differs in return type" type of error if you're using VC++. This is because method/function signatures don't incorporate the return type. I'm guessing it's because of the ambiguity it can cause if the return value isn't being assigned to anything.E.

G int iMyvar = object.method(); // obvious what type should be returned Contrast with:- object.method(); // which overload would the compiler call if return type was part of signature? Ambiguos.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.