QSlotObjectBase: document relation between m_impl and Operation better
Change-Id: I02bfe1857a9c2b781f7ad891e813fd6818fab671 Reviewed-by: Ivan Tkachenko <me@ratijas.tk> Reviewed-by: Lars Knoll <lars.knoll@qt.io> Reviewed-by: Thiago Macieira <thiago.macieira@intel.com>
This commit is contained in:
parent
d179ec6ca4
commit
3c683a8a8d
@ -353,10 +353,13 @@ namespace QtPrivate {
|
||||
QAtomicInt m_ref;
|
||||
// don't use virtual functions here; we don't want the
|
||||
// compiler to create tons of per-polymorphic-class stuff that
|
||||
// we'll never need. We just use one function pointer.
|
||||
// we'll never need. We just use one function pointer, and the
|
||||
// Operations enum below to distinguish requests
|
||||
typedef void (*ImplFn)(int which, QSlotObjectBase* this_, QObject *receiver, void **args, bool *ret);
|
||||
const ImplFn m_impl;
|
||||
protected:
|
||||
// The operations that can be requested by calls to m_impl,
|
||||
// see the member functions that call m_impl below for details
|
||||
enum Operation {
|
||||
Destroy,
|
||||
Call,
|
||||
|
Loading…
Reference in New Issue
Block a user