do I understand C++ wrong?

[MoonKid]

It is a simple problem.

The compiler (mingw32) says
[error]
main.cpp:27: error: no matching function for call to `ClassB::Function()'
main.cpp:17: note: candidates are: bool ClassB::Function(const char*)
[/error]

Code: [Select]

#include <iostream>

class ClassA
{
    public:
        bool Function ()
        {
            return true;
        }
};


class ClassB : public ClassA
{
    public:
        bool Function (const char* str)
        {
            return true;
        }
};


int main()
{
ClassB b;

b.Function();

return 0;
}

I do not understand the compilers problem.
Because A::Function and B:Function has different names because the
signaturs (name+parameters) are different.
Shouldn't it work in iso-c++? Is it a compiler problem or I am wrong
understanding standard c++?

[PChris]

You have to pass the parameter as well
e.g: Function("Hello");

[MoonKid]

You have to pass the parameter as well
e.g: Function("Hello");

No, I do not want to call ClassB::Function. I want to call ClassA::Function. I think the compiler should know that because of the signature.

I know I could call it like that
b.ClassA::Function()

But the compiler should know it by itsefl.

[PChris]

I don't really understand you...
If there is a function in ClassB, why should the compiler search the function in ClassA?

[MoonKid]

If there is a function in ClassB, why should the compiler search the function in ClassA?

The compiler generates symbols (names) for functions while compiletime.

"bool ClassA::Function()" is a different name instead of "bool ClassB::Function(const char*)".
Not because of A and B. Because of the signature of the methodes.
A methode name is generated on functionname+parameters, that is what is called "signature of a function".

That is what I have learned about compilers.

[sethjackson]

The ClassB::Function(const char* str) is different than the ClassA::Function(). You declare ClassB, and then try not passing a param to Fuction(const char* str). You cannot do this since Fuction(const char* str) requires a param. Some C++ guru could answer this better I'm sure, but that is the way the compiler works AFAIK. So why don't you declare ClassA, and call that Function()?

[MoonKid]

So why don't you declare ClassA, and call that Function()?

I want to have an object with a to Function() methodes, one with and one without a parameter.
Logicly (in my framework) they should be in different classes.

I will think about how to design it compilable

[thomas]

Code: [Select]

class ClassB : public ClassA
{
    public:
        using ClassA::Function;
        bool Function (const char* str)
        {
            return true;
        }
};

[Ceniza]

Your problem is the compiler hides A::Function and it's natural C++ behavior.

You could have lots of different signatures of Function in ClassA. If you make ClassB inherit from ClassA, ClassB will have all those Function too, but if you add a method in ClassB with the name Function (just what you're doing), every inherited signature of Function will be hidden.

To make ClassA::Function visible in ClassB do this (Thomas was faster):

Code: C++

1. class ClassB : public ClassA
2. {
3.     public:
4.         using ClassA::Function;
5.  
6.         bool Function (const char* str)
7.         {
8.             return true;
9.         }
10. };

Another way is to change your main to this:

Code: C++

1. int main()
2. {
3.         ClassB b;
4.  
5.         b.ClassA::Function();
6.  
7.         return 0;
8. }