2009/8/22 Jan Hudec :
> On Thu, Aug 20, 2009 at 22:09:21 -0400, Yu Feng wrote:
>> GError doesn't support error wrapping as Java does. Is GLib is purposely
>> avoiding it?
>> If not, it will become a useful feature as the number of libraries that
>> uses GError grows, as the feature has already been
On Thu, 20 Aug 2009 at 22:09:21 -0400, Yu Feng wrote:
> However, because
> GError is always accessed by pointers and no GLib program is supposed to
> statically allocate memory for GError
Er, is nobody supposed to allocate GErrors statically? That's the first I'd
heard of it...
In code using dbus
On Sat, Aug 22, 2009 at 11:52:01 -0400, Yu Feng wrote:
> On Sat, 2009-08-22 at 09:24 +0200, Jan Hudec wrote:
> [...]
> > Well, so the code further up the call stack is not going to look at the
> > inner exception anyway except to print it to the operator, right? But for
> > that, it's enough to emb
On Thu, Aug 20, 2009 at 22:09:21 -0400, Yu Feng wrote:
> GError doesn't support error wrapping as Java does. Is GLib is purposely
> avoiding it?
> If not, it will become a useful feature as the number of libraries that
> uses GError grows, as the feature has already been proved useful in
> Java, (i
On Sat, 2009-08-22 at 09:24 +0200, Jan Hudec wrote:
> On Thu, Aug 20, 2009 at 22:09:21 -0400, Yu Feng wrote:
> > GError doesn't support error wrapping as Java does. Is GLib is purposely
> > avoiding it?
> > If not, it will become a useful feature as the number of libraries that
> > uses GError grow
Dear List,
GError doesn't support error wrapping as Java does. Is GLib is purposely
avoiding it?
If not, it will become a useful feature as the number of libraries that
uses GError grows, as the feature has already been proved useful in
Java, (indicated in this article):
http://tutorials.jenkov.c
