Qt does not warn about undeclared signals

**jamadagni** · 17th February 2006, 08:31

This morning I wrote a line of code connecting the click (sic) signal of a pushbutton to the quit slot of an app and was wondering why the app was not closing upon clicking the button.

Later only an examination using KDiff with another file showed me that I had written click instead of clicked.

But I am very sure I got no errors or even warnings using compile time. Why is this? I should presume that just like undeclared variables or functions are reported as errors, undeclared signals (and slots) should also be reported as errors.

Does anyone else see this behaviour? Shall I file a bug?

**guilugi** · 17th February 2006, 09:04

Hello,

In release mode, Qt doesn't throw warning for undefined SIGNAL(...) or SLOT(...).
If you want to catch those warnings, I think you'll need the debug mode.

Guilugi