AuroraMiddleware/qt5base-lts
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Doc: remove erroneous statement that signals can't have return types

Browse Source 
They can (it's just very, very unusual).

Fixes: QTBUG-116695
Pick-to: 6.5 6.6
Change-Id: I2b24e1d3cad44897906efffd178178f1542e67f2
Reviewed-by: Giuseppe D'Angelo <giuseppe.dangelo@kdab.com>
This commit is contained in:
Thiago Macieira 2023-09-03 12:04:35 -07:00
parent a0b7eee6c6
commit 40e9e42bc6
1 changed files with 1 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
src/corelib/doc/src/objectmodel/signalsandslots.qdoc
View File

@ -110,8 +110,7 @@
when the signal is emitted. when the signal is emitted.
Signals are automatically generated by the \l moc and must not be Signals are automatically generated by the \l moc and must not be
implemented in the \c .cpp file. They can never have return types implemented in the \c .cpp file.
(i.e. use \c void).
A note about arguments: Our experience shows that signals and slots A note about arguments: Our experience shows that signals and slots
are more reusable if they do not use special types. If are more reusable if they do not use special types. If