[Bug 21594] Implement being a Handler

[bugzilla-daemon at freedesktop.org]

http://bugs.freedesktop.org/show_bug.cgi?id=21594





--- Comment #8 from Simon McVittie <simon.mcvittie at collabora.co.uk>  2009-05-19 05:34:15 PST ---
(In reply to comment #6)
> Why is Q_DISABLE_COPY(MethodInvocationContext) in the private: section? Other
> classes have it as the first thing inside class ____ {

It's a matter of taste - the macro expands to a private copy-constructor that
asserts, or some such. It includes a private: prefix, so whatever section
you're in before the macro, you'll be in a private: section afterwards: as a
result, it's good style to put it inside a private: section (like the one
implicitly started by the beginning of the class declaration) so the implicit
becoming-private has no effect.

I've been considering it to be boilerplate similar to Q_OBJECT, and so putting
it at the top next to Q_OBJECT (which has a similar auto-private effect), but
in the private: section at the end works equally well.


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.