Allow explicit object registration.

Allow explicit object registration.

This also allows explicit object *un*registration, which means that the object
lifecycle (as exposed to the bus) is now divorced from the object lifecycle as a
C++ object. This allows things like e.g. unregistering an object now but running
its cleanup "later".

BUG=chromium-os:9628
TEST=Adhoc
Built, ran, connected to 3G.

Change-Id: Icfdb96ff47bb6a0d5e86a0774981906f20304c88
Signed-off-by: Elly Jones <ellyjones@chromium.org>;
Signed-off-by: Jason Glasgow <jglasgow@chromium.org>;

Committed: http://chrome-svn/viewvc/chromeos?view=rev&revision=f5a3f7a

[Jason Glasgow, 2011-02-07 20:00:48]

LGTM

http://codereview.chromium.org/6250197/diff/1/include/dbus-c++/object.h
File include/dbus-c++/object.h (right):

http://codereview.chromium.org/6250197/diff/1/include/dbus-c++/object.h#newco...
include/dbus-c++/object.h:56: virtual void register_obj() = 0;
As discussed, exposing register_obj() does not really help because it is always
called in the constructor.  A case could be made for a constructor that does not
call register_obj() and allows one to invoke register_obj() when appropriate.

No need to change this CL.  We can add that functionality when needed.