Send Gtkmm-forge mailing list submissions to
[email protected]
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
[email protected]
You can reach the person managing the list at
[email protected]
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. Do not try to unsubscribe gtkmm-forge from gtkmm-list.
Today's Topics:
1. [Bug 580507] New: Glib::ustring::const_iterator has not the
same interface as std::string::const_iterator
(gtkmm (bugzilla.gnome.org))
2. [Bug 580507] Glib::ustring::const_iterator has not the same
interface as std::string::const_iterator (gtkmm (bugzilla.gnome.org))
3. [Bug 561885] Glib::Source - mistunderstanding of the
'destroy' from C GSource -> bad impl + memory problems?
(glibmm (bugzilla.gnome.org))
4. [Bug 561885] Glib::Source - mistunderstanding of the
'destroy' from C GSource -> bad impl + memory problems?
(glibmm (bugzilla.gnome.org))
5. [Bug 506885] Stock ID stuff needs documentation
(gtkmm (bugzilla.gnome.org))
6. [Bug 578115] Gio::File::make_directory_with_parents() is not
defined! (glibmm (bugzilla.gnome.org))
7. [Bug 580773] New: const and non-const Glib::ustring iterators
cannot be compared (glibmm (bugzilla.gnome.org))
----------------------------------------------------------------------
Message: 1
Date: Mon, 27 Apr 2009 21:15:48 +0000 (UTC)
From: "gtkmm (bugzilla.gnome.org)"
<[email protected]>
Subject: [gtkmm bugzilla] [Bug 580507] New:
Glib::ustring::const_iterator has not the same interface as
std::string::const_iterator
To: [email protected]
Message-ID: <[email protected]/>
Content-Type: text/plain; charset=utf-8
If you have any questions why you received this email, please see the text at
the end of this email. Replies to this email are NOT read, please see the text
at the end of this email. You can add comments to this bug at:
http://bugzilla.gnome.org/show_bug.cgi?id=580507
gtkmm | TreeView | Ver: unspecified
Summary: Glib::ustring::const_iterator has not the same interface
as std::string::const_iterator
Product: gtkmm
Version: unspecified
Platform: Other
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: TreeView
AssignedTo: [email protected]
ReportedBy: [email protected]
QAContact: [email protected]
GNOME version: Unspecified
GNOME milestone: Unspecified
#include <iostream>
#include <glibmm.h>
int main() {
std::string str("Hello") ;
for ( std::string::const_iterator it = str.begin() ; it != str.end() ;
++ it )
;
Glib::ustring ustr("Hello") ;
for ( Glib::ustring::const_iterator it = ustr.begin() ; it !=
ustr.end() ; ++ it )
;
return 0 ;
}
When compiling, I get the following
test.cpp:18: erreur: no match for ?operator!=? in ?it !=
Glib::ustring::end()()?
Chris Vine suggests to switch from the single templated
template <class T>
bool operator!=(const ustring_Iterator<T>& lhs, const ustring_Iterator<T>& rhs)
to the twin templated
template <class T1, class T2>
bool operator!=(const ustring_Iterator<T1>& lhs, const ustring_Iterator<T2>&
rhs)
to solve this problem. But I am not enough expert to recommend this patch.
Regards,
Fran?ois
--
See http://bugzilla.gnome.org/page.cgi?id=email.html for more info about why
you received
this email, why you can't respond via email, how to stop receiving
emails (or reduce the number you receive), and how to contact someone
if you are having problems with the system.
You can add comments to this bug at
http://bugzilla.gnome.org/show_bug.cgi?id=580507.
------------------------------
Message: 2
Date: Mon, 27 Apr 2009 22:00:25 +0000 (UTC)
From: "gtkmm (bugzilla.gnome.org)"
<[email protected]>
Subject: [gtkmm bugzilla] [Bug 580507] Glib::ustring::const_iterator
has not the same interface as std::string::const_iterator
To: [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8
If you have any questions why you received this email, please see the text at
the end of this email. Replies to this email are NOT read, please see the text
at the end of this email. You can add comments to this bug at:
http://bugzilla.gnome.org/show_bug.cgi?id=580507
gtkmm | TreeView | Ver: unspecified
Jonathon Jongsma (jonner) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |[email protected]
------- Comment #1 from Jonathon Jongsma (jonner) 2009-04-27 22:00 UTC -------
Thanks for filing the bug. just adding a link to the original email thread for
reference: http://mail.gnome.org/archives/gtkmm-list/2009-April/msg00093.html
--
See http://bugzilla.gnome.org/page.cgi?id=email.html for more info about why
you received
this email, why you can't respond via email, how to stop receiving
emails (or reduce the number you receive), and how to contact someone
if you are having problems with the system.
You can add comments to this bug at
http://bugzilla.gnome.org/show_bug.cgi?id=580507.
------------------------------
Message: 3
Date: Tue, 28 Apr 2009 04:08:14 +0000 (UTC)
From: "glibmm (bugzilla.gnome.org)"
<[email protected]>
Subject: [gtkmm bugzilla] [Bug 561885] Glib::Source -
mistunderstanding of the 'destroy' from C GSource -> bad impl +
memory
problems?
To: [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8
If you have any questions why you received this email, please see the text at
the end of this email. Replies to this email are NOT read, please see the text
at the end of this email. You can add comments to this bug at:
http://bugzilla.gnome.org/show_bug.cgi?id=561885
glibmm | general | Ver: 2.18.x
Jonathon Jongsma (jonner) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |[email protected]
------- Comment #4 from Jonathon Jongsma (jonner) 2009-04-28 04:08 UTC -------
For what it's worth, I spent most of the evening looking at this bug and I'm
not really much closer to a solution. Ideally, we would simply be able to use
the 'finalize' vfunc, but GSource doesnt' allow us to store arbitrary data
(i.e. a pointer to the wrapper) in it, so we are not able to determine the
proper wrapper object at that point. So I guess the destroy_notify callback
was used as a workaround for these deficiencies, but it does certainly seem to
have problems.
One potential idea I thought about was passing a slightly larger struct size to
g_source_new() and then storing a pointer to the wrapper in the larger struct,
e.g.:
struct GSourceWithWrapper {
GSource source;
Glib::Source* wrapper;
};
however, this only helps when we're creating a new Glib::Source from glibmm.
it doesn't help us at all if we're creating a wrapper object for an existing
GSource* object.
So I'm out of ideas for now.
--
See http://bugzilla.gnome.org/page.cgi?id=email.html for more info about why
you received
this email, why you can't respond via email, how to stop receiving
emails (or reduce the number you receive), and how to contact someone
if you are having problems with the system.
You can add comments to this bug at
http://bugzilla.gnome.org/show_bug.cgi?id=561885.
------------------------------
Message: 4
Date: Tue, 28 Apr 2009 04:44:30 +0000 (UTC)
From: "glibmm (bugzilla.gnome.org)"
<[email protected]>
Subject: [gtkmm bugzilla] [Bug 561885] Glib::Source -
mistunderstanding of the 'destroy' from C GSource -> bad impl +
memory
problems?
To: [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8
If you have any questions why you received this email, please see the text at
the end of this email. Replies to this email are NOT read, please see the text
at the end of this email. You can add comments to this bug at:
http://bugzilla.gnome.org/show_bug.cgi?id=561885
glibmm | general | Ver: 2.18.x
Jonathon Jongsma (jonner) changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Ever Confirmed|0 |1
------- Comment #5 from Jonathon Jongsma (jonner) 2009-04-28 04:44 UTC -------
OK, so I do have one other idea -- keep our own map of GSource*-to-wrapper so
that we can use the finalize vfunc and look up a C object's wrapper object when
finalize gets called. This wouldn't be great for performance since we'd
probably have to protect the map with a mutex to make it thread-safe, but I
don't imagine that creating and destroying GSource objects is going to be on
the critical path for performance in any applications...
--
See http://bugzilla.gnome.org/page.cgi?id=email.html for more info about why
you received
this email, why you can't respond via email, how to stop receiving
emails (or reduce the number you receive), and how to contact someone
if you are having problems with the system.
You can add comments to this bug at
http://bugzilla.gnome.org/show_bug.cgi?id=561885.
------------------------------
Message: 5
Date: Tue, 28 Apr 2009 07:31:01 +0000 (UTC)
From: "gtkmm (bugzilla.gnome.org)"
<[email protected]>
Subject: [gtkmm bugzilla] [Bug 506885] Stock ID stuff needs
documentation
To: [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8
If you have any questions why you received this email, please see the text at
the end of this email. Replies to this email are NOT read, please see the text
at the end of this email. You can add comments to this bug at:
http://bugzilla.gnome.org/show_bug.cgi?id=506885
gtkmm | reference documentation | Ver: unspecified
Johannes Schmid changed:
What |Removed |Added
----------------------------------------------------------------------------
Attachment #133400|none |committed
Flag| |
Status|NEW |RESOLVED
Resolution| |FIXED
--
See http://bugzilla.gnome.org/page.cgi?id=email.html for more info about why
you received
this email, why you can't respond via email, how to stop receiving
emails (or reduce the number you receive), and how to contact someone
if you are having problems with the system.
You can add comments to this bug at
http://bugzilla.gnome.org/show_bug.cgi?id=506885.
------------------------------
Message: 6
Date: Wed, 29 Apr 2009 05:01:29 +0000 (UTC)
From: "glibmm (bugzilla.gnome.org)"
<[email protected]>
Subject: [gtkmm bugzilla] [Bug 578115]
Gio::File::make_directory_with_parents() is not defined!
To: [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8
If you have any questions why you received this email, please see the text at
the end of this email. Replies to this email are NOT read, please see the text
at the end of this email. You can add comments to this bug at:
http://bugzilla.gnome.org/show_bug.cgi?id=578115
glibmm | giomm | Ver: 2.18.x
------- Comment #9 from Jos? Alburquerque 2009-04-29 05:01 UTC -------
> Sorry to interject but it may be necessary to also include it in the 2-16
> branch.
I'm wrong about this. g_file_make_directory_with_parents wasn't introduced
until 2-18[1].
[1] http://library.gnome.org/devel/gio/2.18/ix02.html
--
See http://bugzilla.gnome.org/page.cgi?id=email.html for more info about why
you received
this email, why you can't respond via email, how to stop receiving
emails (or reduce the number you receive), and how to contact someone
if you are having problems with the system.
You can add comments to this bug at
http://bugzilla.gnome.org/show_bug.cgi?id=578115.
------------------------------
Message: 7
Date: Wed, 29 Apr 2009 16:19:16 +0000 (UTC)
From: "glibmm (bugzilla.gnome.org)"
<[email protected]>
Subject: [gtkmm bugzilla] [Bug 580773] New: const and non-const
Glib::ustring iterators cannot be compared
To: [email protected]
Message-ID: <[email protected]/>
Content-Type: text/plain; charset=utf-8
If you have any questions why you received this email, please see the text at
the end of this email. Replies to this email are NOT read, please see the text
at the end of this email. You can add comments to this bug at:
http://bugzilla.gnome.org/show_bug.cgi?id=580773
glibmm | strings | Ver: 2.20.x
Summary: const and non-const Glib::ustring iterators cannot be
compared
Product: glibmm
Version: 2.20.x
Platform: Other
OS/Version: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: strings
AssignedTo: [email protected]
ReportedBy: [email protected]
QAContact: [email protected]
GNOME version: 2.25/2.26
GNOME milestone: Unspecified
Please describe the problem:
comparison of const and non-const Glib::ustring iterators fails to compile
because of template type mismatch of the iterator comparison operators
Patch allowing implicit type conversion to follow.
Steps to reproduce:
1.
2.
3.
Actual results:
Expected results:
Does this happen every time?
Other information:
--
See http://bugzilla.gnome.org/page.cgi?id=email.html for more info about why
you received
this email, why you can't respond via email, how to stop receiving
emails (or reduce the number you receive), and how to contact someone
if you are having problems with the system.
You can add comments to this bug at
http://bugzilla.gnome.org/show_bug.cgi?id=580773.
------------------------------
------------------------------------------------------------------------------
Register Now & Save for Velocity, the Web Performance & Operations
Conference from O'Reilly Media. Velocity features a full day of
expert-led, hands-on workshops and two days of sessions from industry
leaders in dedicated Performance & Operations tracks. Use code vel09scf
and Save an extra 15% before 5/3. http://p.sf.net/sfu/velocityconf
------------------------------
_______________________________________________
Gtkmm-forge mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/gtkmm-forge
End of Gtkmm-forge Digest, Vol 35, Issue 8
******************************************
_______________________________________________
gtkmm-list mailing list
[email protected]
http://mail.gnome.org/mailman/listinfo/gtkmm-list
