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 511136] TreeView::get_cursor() may return an invalid
TreePath instance (gtkmm (bugzilla.gnome.org))
2. [Bug 511136] TreeView::get_cursor() may return an invalid
TreePath instance (gtkmm (bugzilla.gnome.org))
3. [Bug 511136] TreeView::get_cursor() may return an invalid
TreePath instance (gtkmm (bugzilla.gnome.org))
4. [Bug 571700] New: Compilation warnings with gcc 4.4
(glibmm (bugzilla.gnome.org))
5. [Bug 571837] New: snprintf used without declaration
(gnomemm (bugzilla.gnome.org))
6. [Bug 571837] snprintf used without declaration
(gnomemm (bugzilla.gnome.org))
7. [Bug 571838] New: geglbuffer-clock.cc compiles with warnings
(gnomemm (bugzilla.gnome.org))
----------------------------------------------------------------------
Message: 1
Date: Thu, 12 Feb 2009 16:02:44 +0000 (UTC)
From: "gtkmm (bugzilla.gnome.org)"
<[email protected]>
Subject: [gtkmm bugzilla] [Bug 511136] TreeView::get_cursor() may
return an invalid TreePath instance
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=511136
gtkmm | TreeView | Ver: 2.12.x
------- Comment #9 from Murray Cumming 2009-02-12 16:02 UTC -------
> TreePath does not, in any way, represent a pointer or pointer-like data
> structure. It isn't a handle. The interface is that of an STL container. Also,
> there is no need to make a distinction between an invalid TreePath and an
> empty
> one.
We don't make a distinction. We do say that a (internally) invalid one is as
useless as an empty one. As far as I know there is know, and empty TreePath has
no meaning other than, "no path".
A std::vector can be empty too. It doesn't have operator bool() for that. Are
you saying that you'd be happy with just making empty() check for an null
gobj()?
> Eeek, no. Output parameters are a horrible last resort. And having such an
> overload *in addition* to some other means to represent that state is just
> ugly.
I'm not sure anymore what you actually want.
--
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=511136.
------------------------------
Message: 2
Date: Thu, 12 Feb 2009 16:48:17 +0000 (UTC)
From: "gtkmm (bugzilla.gnome.org)"
<[email protected]>
Subject: [gtkmm bugzilla] [Bug 511136] TreeView::get_cursor() may
return an invalid TreePath instance
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=511136
gtkmm | TreeView | Ver: 2.12.x
------- Comment #10 from Daniel Elstner 2009-02-12 16:48 UTC -------
(In reply to comment #9)
> We don't make a distinction. We do say that a (internally) invalid one is as
> useless as an empty one. As far as I know there is know, and empty TreePath
> has
> no meaning other than, "no path".
But it is still a valid container in one case but not in another.
So why have two internal states to say the same thing?
> A std::vector can be empty too. It doesn't have operator bool() for that.
But std::vector::empty() does not attempt to handle the situation where the
vector object is corrupted and in an invalid state.
> Are
> you saying that you'd be happy with just making empty() check for an null
> gobj()?
Er, no. That's how it is right now.
bool TreePath::empty() const
{
if(!gobject_)
return false;
return (gtk_tree_path_get_depth(gobject_) == 0);
}
> I'm not sure anymore what you actually want.
Ditch the check for NULL and operator bool(), and custom-code
TreeView::get_cursor() to return an empty but valid path if the GTK+ function
returns NULL.
--
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=511136.
------------------------------
Message: 3
Date: Fri, 13 Feb 2009 18:17:03 +0000 (UTC)
From: "gtkmm (bugzilla.gnome.org)"
<[email protected]>
Subject: [gtkmm bugzilla] [Bug 511136] TreeView::get_cursor() may
return an invalid TreePath instance
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=511136
gtkmm | TreeView | Ver: 2.12.x
------- Comment #11 from Daniel Elstner 2009-02-13 18:17 UTC -------
OK. Murray and I discussed the problem on IRC. We agreed on removing operator
bool() again, and making sure that the object is never in an invalid state to
begin with. However, this should be done in a generic way and therefore needs
to go into the constructor.
Unfortunately the constructor is auto-generated, and it is not possible to
easily override the autogeneration. For this reason this won't be a quick fix,
unfortunately, but will have to wait until someone finds the time to add
another exception flag to gmmproc to suppress the autogeneration of the
constructor.
However, the removal of operator bool() doesn't have to wait until then. In
fact, it needs to be removed before the API freeze, so I'll do it right 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=511136.
------------------------------
Message: 4
Date: Sat, 14 Feb 2009 06:40:36 +0000 (UTC)
From: "glibmm (bugzilla.gnome.org)"
<[email protected]>
Subject: [gtkmm bugzilla] [Bug 571700] New: Compilation warnings with
gcc 4.4
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=571700
glibmm | build | Ver: 2.19.x
Summary: Compilation warnings with gcc 4.4
Product: glibmm
Version: 2.19.x
Platform: Other
OS/Version: Linux
Status: UNCONFIRMED
Severity: minor
Priority: Normal
Component: build
AssignedTo: [email protected]
ReportedBy: [email protected]
QAContact: [email protected]
GNOME version: Unspecified
GNOME milestone: Unspecified
We're seeing compile warnings with g++ 4.4, coming from refptr.h:
/usr/include/glibmm-2.4/glibmm/refptr.h: In constructor
?WinMain::WinMain(bool)?:
/usr/include/glibmm-2.4/glibmm/refptr.h:172: warning: dereferencing pointer
?<anonymous>? does break strict-aliasing rules
/usr/include/glibmm-2.4/glibmm/refptr.h:285: warning: dereferencing pointer
?<anonymous>? does break strict-aliasing rules
/usr/lib/gcc/i386-redhat-linux/4.4.0/../../../../include/c++/4.4.0/bits/stl_list.h:219:
note: initialized from here
/usr/include/glibmm-2.4/glibmm/refptr.h: In constructor
?WinMain::WinMain(bool)?:
/usr/include/glibmm-2.4/glibmm/refptr.h:172: warning: dereferencing pointer
?<anonymous>? does break strict-aliasing rules
/usr/include/glibmm-2.4/glibmm/refptr.h:285: warning: dereferencing pointer
?<anonymous>? does break strict-aliasing rules
/usr/lib/gcc/i386-redhat-linux/4.4.0/../../../../include/c++/4.4.0/bits/stl_list.h:219:
note: initialized from here
--
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=571700.
------------------------------
Message: 5
Date: Sun, 15 Feb 2009 15:12:17 +0000 (UTC)
From: "gnomemm (bugzilla.gnome.org)"
<[email protected]>
Subject: [gtkmm bugzilla] [Bug 571837] New: snprintf used without
declaration
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=571837
gnomemm | geglmm | Ver: unspecified
Summary: snprintf used without declaration
Product: gnomemm
Version: unspecified
Platform: Other
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: geglmm
AssignedTo: [email protected]
ReportedBy: [email protected]
QAContact: [email protected]
GNOME version: Unspecified
GNOME milestone: Unspecified
There is a missing #include <cstdio> in the hello-world.cc that makes snprintf
be used without declaration. This is an error with gcc 4.4.
--
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=571837.
------------------------------
Message: 6
Date: Sun, 15 Feb 2009 15:13:05 +0000 (UTC)
From: "gnomemm (bugzilla.gnome.org)"
<[email protected]>
Subject: [gtkmm bugzilla] [Bug 571837] snprintf used without
declaration
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=571837
gnomemm | geglmm | Ver: unspecified
------- Comment #1 from dodji seketeli 2009-02-15 15:13 UTC -------
Created an attachment (id=128776)
--> (http://bugzilla.gnome.org/attachment.cgi?id=128776&action=view)
Fixes the problem
--
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=571837.
------------------------------
Message: 7
Date: Sun, 15 Feb 2009 15:15:02 +0000 (UTC)
From: "gnomemm (bugzilla.gnome.org)"
<[email protected]>
Subject: [gtkmm bugzilla] [Bug 571838] New: geglbuffer-clock.cc
compiles with warnings
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=571838
gnomemm | geglmm | Ver: unspecified
Summary: geglbuffer-clock.cc compiles with warnings
Product: gnomemm
Version: unspecified
Platform: Other
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: geglmm
AssignedTo: [email protected]
ReportedBy: [email protected]
QAContact: [email protected]
GNOME version: Unspecified
GNOME milestone: Unspecified
geglbuffer-clock.cc has some unused variables that lead to gcc emitting
warnings at compile time.
--
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=571838.
------------------------------
------------------------------------------------------------------------------
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
-Strategies to boost innovation and cut costs with open source participation
-Receive a $600 discount off the registration fee with the source code: SFAD
http://p.sf.net/sfu/XcvMzF8H
------------------------------
_______________________________________________
Gtkmm-forge mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/gtkmm-forge
End of Gtkmm-forge Digest, Vol 33, Issue 8
******************************************
_______________________________________________
gtkmm-list mailing list
[email protected]
http://mail.gnome.org/mailman/listinfo/gtkmm-list
