On Fri, Nov 29, 2013 at 5:56 PM, Markus Armbruster arm...@redhat.com wrote:
Peter Crosthwaite peter.crosthwa...@xilinx.com writes:
On Fri, Nov 29, 2013 at 1:03 AM, Markus Armbruster arm...@redhat.com wrote:
Paolo Bonzini pbonz...@redhat.com writes:
Il 28/11/2013 14:23, Igor Mammedov ha
On Wed, 27 Nov 2013 21:58:18 -0700
Eric Blake ebl...@redhat.com wrote:
On 11/27/2013 06:24 PM, Igor Mammedov wrote:
in case if caller setting property doesn't care about error and
passes in NULL as errp argument but error occurs in property setter,
it is silently discarded leaving object
On Thu, 28 Nov 2013 15:10:50 +1000
Peter Crosthwaite peter.crosthwa...@xilinx.com wrote:
Hi,
On Thu, Nov 28, 2013 at 11:24 AM, Igor Mammedov imamm...@redhat.com wrote:
in case if caller setting property doesn't care about error and
passes in NULL as errp argument but error occurs in
Il 28/11/2013 14:23, Igor Mammedov ha scritto:
object_property_set(Foo, bar, baz, abort_on_err);
that is just another way to put burden on caller, instead of doing it
in one place.
It's also much more self-documenting.
The problem is that there is one very good case where you want the
Am 28.11.2013 14:48, schrieb Igor Mammedov:
On Thu, 28 Nov 2013 14:42:38 +0100
Andreas Färber afaer...@suse.de wrote:
I will be more than happy to review and apply your patch (or contribute
further ones) going through (mis)uses of error_is_set().
I've sent such one for target-i386/cpu.c see
Igor Mammedov imamm...@redhat.com writes:
On Thu, 28 Nov 2013 15:10:50 +1000
Peter Crosthwaite peter.crosthwa...@xilinx.com wrote:
Hi,
On Thu, Nov 28, 2013 at 11:24 AM, Igor Mammedov imamm...@redhat.com wrote:
in case if caller setting property doesn't care about error and
passes in
Paolo Bonzini pbonz...@redhat.com writes:
Il 28/11/2013 14:23, Igor Mammedov ha scritto:
object_property_set(Foo, bar, baz, abort_on_err);
that is just another way to put burden on caller, instead of doing it
in one place.
It's also much more self-documenting.
The problem is that there
On Fri, Nov 29, 2013 at 1:03 AM, Markus Armbruster arm...@redhat.com wrote:
Paolo Bonzini pbonz...@redhat.com writes:
Il 28/11/2013 14:23, Igor Mammedov ha scritto:
object_property_set(Foo, bar, baz, abort_on_err);
that is just another way to put burden on caller, instead of doing it
in
Peter Crosthwaite peter.crosthwa...@xilinx.com writes:
On Fri, Nov 29, 2013 at 1:03 AM, Markus Armbruster arm...@redhat.com wrote:
Paolo Bonzini pbonz...@redhat.com writes:
Il 28/11/2013 14:23, Igor Mammedov ha scritto:
object_property_set(Foo, bar, baz, abort_on_err);
that is just
in case if caller setting property doesn't care about error and
passes in NULL as errp argument but error occurs in property setter,
it is silently discarded leaving object in undefined state.
As result it leads to hard to find bugs, so if caller doesn't
care about error it must be sure that
On 11/27/2013 06:24 PM, Igor Mammedov wrote:
in case if caller setting property doesn't care about error and
passes in NULL as errp argument but error occurs in property setter,
it is silently discarded leaving object in undefined state.
As result it leads to hard to find bugs, so if caller
Hi,
On Thu, Nov 28, 2013 at 11:24 AM, Igor Mammedov imamm...@redhat.com wrote:
in case if caller setting property doesn't care about error and
passes in NULL as errp argument but error occurs in property setter,
it is silently discarded leaving object in undefined state.
As result it leads
Peter Crosthwaite peter.crosthwa...@xilinx.com writes:
Hi,
On Thu, Nov 28, 2013 at 11:24 AM, Igor Mammedov imamm...@redhat.com wrote:
in case if caller setting property doesn't care about error and
passes in NULL as errp argument but error occurs in property setter,
it is silently discarded
13 matches
Mail list logo
