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

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

To subscribe or unsubscribe via the World Wide Web, visit
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
Date: Sun, 16 Feb 2003 05:53:08 -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.


Changed by murrayc usa net 

--- shadow/101878	Sat Feb  1 17:14:19 2003
+++ shadow/101878.tmp.5293	Sun Feb 16 05:53:08 2003
@@ -108,6 +108,25 @@
 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.
+------- Additional Comments From murrayc usa net  2003-02-16 05:53 -------
+>> 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.
+Do you mean "make it feasible to add operator overrides to
+Glib::Object-derived classes"? I can't think of any time when that
+would be useful. Again, until we actually need it, I see no need to 
+confuse the RefPtr API.
+> But you can't stop people from doing it if they are
+> determined to do so.
+Yes, and those people know that they are doing something wrong and can
+deal with the consequences.


Gtkmm-forge mailing list
Gtkmm-forge lists sourceforge net

End of Gtkmm-forge Digest

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]