Soft-deprecate obscure feature on property getters returning pointers

moc actually generates the right code for getters returning a pointer
to the type in question, or a reference to the type (a reference, one
would assume, does not require code changes). However, the same
extension is not valid for the setter: it can't receive the new value
by pointer.

Therefore, let's soft-deprecate the feature by removing its existence
from the documentation.

Task-number: QTBUG-33091
Change-Id: I27844213e051ec7fafeb4744089a0653aea6f1f3
Reviewed-by: Olivier Goffart <ogoffart@woboq.com>
Reviewed-by: Jerome Pasion <jerome.pasion@digia.com>
This commit is contained in:
Thiago Macieira 2013-08-20 11:30:11 -07:00 committed by The Qt Project
parent ca772b2f2f
commit 362ea2dede

View File

@ -67,7 +67,7 @@
\li A \c READ accessor function is required if no \c MEMBER variable was \li A \c READ accessor function is required if no \c MEMBER variable was
specified. It is for reading the property value. Ideally, a const function specified. It is for reading the property value. Ideally, a const function
is used for this purpose, and it must return either the property's type or a is used for this purpose, and it must return either the property's type or a
pointer or reference to that type. e.g., QWidget::focus is a read-only const reference to that type. e.g., QWidget::focus is a read-only
property with \c READ function, QWidget::hasFocus(). property with \c READ function, QWidget::hasFocus().
\li A \c WRITE accessor function is optional. It is for setting the \li A \c WRITE accessor function is optional. It is for setting the