[gtkmm] Gtkmm-forge digest, Vol 1 #348 - 1 msg

[gtkmm-forge-request lists sourceforge net]

Send Gtkmm-forge mailing list submissions to
	gtkmm-forge lists sourceforge net

To subscribe or unsubscribe via the World Wide Web, visit
	https://lists.sourceforge.net/lists/listinfo/gtkmm-forge
or, via email, send a message with subject or body 'help' to
	gtkmm-forge-request lists sourceforge net

You can reach the person managing the list at
	gtkmm-forge-admin lists sourceforge net

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Gtkmm-forge digest..."


gtkmm-forge is the mailing list that receives gtkmm bug reports from bugzilla.  A daily digest is sent to gtkmm-main, to encourage people to help fixing the bugs.


Today's Topics:

   1. [Bug 101878] Changed - Glib::RefPtr<> should have operator*() (bugzilla-daemon widget gnome org)

--__--__--

Message: 1
From: bugzilla-daemon widget gnome org
To: gtkmm-forge lists sourceforge net
Cc: 
Date: Sat,  1 Feb 2003 17:14:19 -0500 (EST)
Subject: [gtkmm bugzilla] [Bug 101878] Changed - Glib::RefPtr<> should have operator*()

Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.

http://bugzilla.gnome.org/show_bug.cgi?id=101878

Changed by michaelj maine rr com 

--- shadow/101878	Fri Jan 31 18:32:27 2003
+++ shadow/101878.tmp.3628	Sat Feb  1 17:14:19 2003
@@ -81,6 +81,33 @@
 
 > 2) It would discourage people from using the much uglier
 > ptr.operator->() mechanism to get at the referenced object directly.
 
 You have not yet shown that it is necessary for anyone to use either
 operator* or the uglier operator-> mechanism.
+
+------- Additional Comments From michaelj maine rr com  2003-02-01 17:14 -------
+>> 1) It would make it feasible to add operators to Glib::Object-based
+>> classes.
+>
+>I don't understand. What would be added to what?
+
+I'm not suggesting any specific changes. I'm just saying that it would
+make it feasible to exploit operators in the Glib::Object hierarchy.
+Facilitating a highly useful programming technique seems to me to be a
+good reason to have the dereferencing operator, even if it isn't going
+to be used immediately.
+
+>> 2) It would discourage people from using the much uglier
+>> ptr.operator->() mechanism to get at the referenced object >directly.
+>
+>You have not yet shown that it is necessary for anyone to use either
+>operator* or the uglier operator-> mechanism.
+
+Nope, that's true. But you can't stop people from doing it if they are
+determined to do so. If you make it possible to use the operator*
+technique rather than the operator-> technique, then I suspect the
+tendency to abuse them would be reduced. I expect that people using
+the operator-> hack would be more likely to keep long-lived copies of
+the dumb pointer, whereas if they can use the operator* to quickly and
+succinctly get very short-lived references to the object, then they're
+less likely to abuse them.




--__--__--

_______________________________________________
Gtkmm-forge mailing list
Gtkmm-forge lists sourceforge net
https://lists.sourceforge.net/lists/listinfo/gtkmm-forge


End of Gtkmm-forge Digest