Why does a wrong override compile?

Asked Aug 23 '13 at 12:43

Active Aug 23 '13 at 13:01

Viewed 101 times

I have this code :

class A
{
    virtual void operator()(std::complex<double>* const input_spectrum, 
                            double* const noise_spectrum) = 0;
};

class B : public A
{
    virtual void operator()(std::complex<double>* input_spectrum, 
                            double* noise_spectrum) override;
}

I don't get why it compiles? The const qualifiers are different, so it should throw an error, doesn't it?. Running under MinGW 4.8

edited Aug 23 '13 at 13:01

codeling

10,672
4
37
67

asked Aug 23 '13 at 12:43

Jean-Michaël Celerier

6,602
3
49
69

6

Top level qualifiers are ignored in function signatures. – jrok Aug 23 '13 at 12:45
Ah, get it, it's because it is a copy of the original pointer so any modification is not important, right ? – Jean-Michaël Celerier Aug 23 '13 at 12:49
http://stackoverflow.com/questions/3683881/functions-with-const-arguments-overloading-follow-up – fen Aug 23 '13 at 12:50
1

@Jean-MichaëlCelerier excatly... like foo(int) and foo(const int) – fen Aug 23 '13 at 12:51
See [this related question](http://stackoverflow.com/questions/18297790/fooling-a-c-compiler-passing-int-instead-of-a-cont-int-into-function/18297802#18297802). – juanchopanza Aug 23 '13 at 12:57

Why does a wrong override compile?

0 Answers0