27118 2009-07-09 07:38:49 -0700 [QT] Wrong of declaration of writeOnlyProperty: READ function is always required. 2010-08-02 09:20:26 -0700 1 1 1 Unclassified WebKit Tools / Tests 528+ (Nightly build) PC Linux RESOLVED WONTFIX Qt P2 Minor --- 0 tonikitoo webkit-unassigned hausmann jedrzej.nowacki laszlo.gombos ossy oldest_to_newest 130661 0 tonikitoo 2009-07-09 07:38:49 -0700 tst_qwebframe.cpp we have: (...) class MyQObject : public QObject { Q_OBJECT (...) Q_PROPERTY(int writeOnlyProperty WRITE setWriteOnlyProperty) (...) which is wrong and triggers a compile warning while building ... (...) /home/agomes/reps/webkit/WebKit/qt/tests/qwebframe/tst_qwebframe.cpp:88: Warning: Property declaration writeOnlyProperty has no READ accessor function. The property will be invalid. (...) --> See statement in http://chaos.troll.no/~tavestbo/webkit/domapi/qobject.html#Q_PROPERTY "...The property name and type and the READ function are required..." 166690 1 jedrzej.nowacki 2009-11-26 03:10:04 -0800 In general Qt discourage to declare write-only properties. In all cases, apart from one, the warning is correct. In this particular case we need a hack to test the JavaScript functionality. In the JavaScript concept of write-only property exists, we can't change it. We can support the feature, but in the same time we discourage to use it. According to logs, there was a bigger discussion about the problem. I'm closing the bug, but if you disagree, feel free to reopen it. 167114 2 laszlo.gombos 2009-11-29 15:36:31 -0800 I looked into this a while bug and draw the same conclusion as Jędrzej. Just for future reference - I think the warning is coming from moc and not from the C/C++ compiler. 258918 3 ossy 2010-08-02 09:16:47 -0700 *** Bug 43356 has been marked as a duplicate of this bug. *** 258921 4 ossy 2010-08-02 09:20:26 -0700 (In reply to comment #2) > I looked into this a while bug and draw the same conclusion as Jędrzej. > > Just for future reference - I think the warning is coming from moc and not from the C/C++ compiler. Yes, this warning is coming from moc, and doesn't block build if we add -Werror option to gcc: https://bugs.webkit.org/show_bug.cgi?id=43191 But unfortunately it makes the compiling step orange on the buildbot. :( Is there a correct way to hide this warning to make the bot green?