[gtkmm] Gtkmm-forge digest, Vol 1 #251 - 2 msgs

[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 88667] Changed - TreeNodeChildren should have a reverse iterator. (bugzilla-daemon widget gnome org)
   2. [Bug 93787] Changed - Outputting ustring with operator << converts implicitly (bugzilla-daemon widget gnome org)

--__--__--

Message: 1
From: bugzilla-daemon widget gnome org
To: gtkmm-forge lists sourceforge net
Cc: 
Date: Thu, 10 Oct 2002 10:14:39 -0400 (EDT)
Subject: [gtkmm bugzilla] [Bug 88667] Changed - TreeNodeChildren should have a reverse iterator.

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=88667

Changed by daniel elstner gmx net 

--- shadow/88667	Sat Jul 27 07:50:38 2002
+++ shadow/88667.tmp.7615	Thu Oct 10 10:14:38 2002
@@ -36,6 +36,17 @@
 them if we add them to all of our STL-style containers.
 
 ------- Additional Comments From murrayc usa net  2002-07-27 07:50 -------
 There are other reverse iterators in gtkmm (grep for rbegin), so this
 would be nice to have. But there is no gtk_tree_model_iter_previous(),
 so it isn't trivial to implement, though it might be possible. Punted.
+
+------- Additional Comments From daniel elstner gmx net  2002-10-10 10:14 -------
+While I agree that reverse iterators would be handy, we can't support
+them as long GTK+ doesn't support them.  And I strongly object against
+introducing functionality that contradicts the way the underlying data
+structures work -- this would violate STL principles.  E.g.
+std::list<> doesn't support random access iterators although it would
+technically be possible.
+
+Murray, is it OK to close this bug?
+



--__--__--

Message: 2
From: bugzilla-daemon widget gnome org
To: gtkmm-forge lists sourceforge net, olau hardworking dk
Cc: 
Date: Thu, 10 Oct 2002 10:26:38 -0400 (EDT)
Subject: [gtkmm bugzilla] [Bug 93787] Changed - Outputting ustring with operator << converts implicitly

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=93787

Changed by daniel elstner gmx net 

--- shadow/93787	Thu Oct  3 16:09:27 2002
+++ shadow/93787.tmp.10335	Thu Oct 10 10:26:38 2002
@@ -222,6 +222,31 @@
 
 This would give a more seamless integration with the standard library.
 I don't think it's possible to guarantee that all characters survive
 the conversion back and forth, but hopefully people will use a locale
 that supports all the characters of their language. So this might be a
 non-existant problem.
+
+------- Additional Comments From daniel elstner gmx net  2002-10-10 10:26 -------
+I think this would create more problems than it solves.
+
+1) Using std::string instead of Glib::ustring for UTF-8 strings would
+lead to unexpected results.
+
+2) Charset conversion is quiet costly and shouldn't be performed in an
+implicit type conversion.
+
+3) The encoding of std::string is undefined and should stay that way.
+ For instance, we always use std::string for filenames because their
+encoding could be either UTF-8 or the locale encoding if
+G_BROKEN_FILENAMES is set.
+
+To summarize, I think it's a bad idea to associate std::string with
+any particular encoding.  The C++ standard library doesn't do that
+either.  Regarding std::ostringstream it's sufficient to write:
+
+Glib::ustring ustr = Glib::locale_to_utf8(stream.str());
+
+That isn't too hard, we should just mention it in the documentation.
+
+--Daniel
+




--__--__--

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


End of Gtkmm-forge Digest