Bernhard Beschow <shentey@gmail.com> writes:
Am 20. Oktober 2023 17:15:04 UTC schrieb "Philippe Mathieu-Daudé"
<philmd@linaro.org>:
Unfortunately v2 was merged as commit 40f8214fcd,
so adapt v3 to clean the mess.
Philippe Mathieu-Daudé (4):
hw/i386/pc: Pass Error** argument to pc_basic_device_init()
hw/i386/pc: Propagate error if HPET device creation failed
hw/i386/pc: Propagate error if PC_SPEAKER device creation failed
I'm not sure if I'd do these first three patches. The reason is that machines
don't inherit from DeviceState and therefore don't have canonical methods such
as realize() to propagate errors. Propagating the errors in the machine init
helper methods seem a bit ad-hoc to me.
The Error interface enables separation of error detection and error
handling. On detection, we create an Error object, and handling
consumes it.
A function that leaves error handling to its callers generally requires
its callees to leave it, too. Use of &error_fatal is wrong then.
Even when error handling need not be left to callers, leaving it can
result in simpler or more robust code.
When a function handles errors itself, say by use of &error_fatal or
error_report(), it's only usable in contexts where this handling is
appropriate.
Sometimes the context is obvious enough, and unlikely to change.
Handling directly is fine then, and can be simpler.
When the context isn't that obvious, leaving error handling to callers
liberates you from thinking about the context, and also enables safe
reuse of the function in other contexts.
I think pc_basic_device_init() doesn't *need* the change, as it's
context is obvious enough. But the change is fine, and if we apply it,
we never have to think about the context again. Matter of taste.