diff options
| author | Markus Armbruster | 2014-05-07 09:53:46 +0200 |
|---|---|---|
| committer | Luiz Capitulino | 2014-05-15 20:00:45 +0200 |
| commit | e2cd0f4fb42b1fae65ad22e8efde9804446e6254 (patch) | |
| tree | f8ea58b96ee1114f9dd0c45d67d567faec516df3 /scripts/switch-timer-api | |
| parent | qapi: Remove unused Visitor callbacks start_handle(), end_handle() (diff) | |
| download | qemu-e2cd0f4fb42b1fae65ad22e8efde9804446e6254.tar.gz qemu-e2cd0f4fb42b1fae65ad22e8efde9804446e6254.tar.xz qemu-e2cd0f4fb42b1fae65ad22e8efde9804446e6254.zip | |
qapi: Replace start_optional()/end_optional() by optional()
Semantics of end_optional() differ subtly from the other end_FOO()
callbacks: when start_FOO() succeeds, the matching end_FOO() gets
called regardless of what happens in between. end_optional() gets
called only when everything in between succeeds as well. Entirely
undocumented, like all of the visitor API.
The only user of Visitor Callback end_optional() never did anything,
and was removed in commit 9f9ab46.
I'm about to clean up error handling in the generated visitor code,
and end_optional() is in my way. No users mean no test cases, and
making non-trivial cleanup transformations without test cases doesn't
strike me as a good idea.
Drop end_optional(), and rename start_optional() to optional(). We
can always go back to a pair of callbacks when we have an actual need.
Signed-off-by: Markus Armbruster <armbru@redhat.com>
Reviewed-by: Eric Blake <eblake@redhat.com>
Signed-off-by: Luiz Capitulino <lcapitulino@redhat.com>
Diffstat (limited to 'scripts/switch-timer-api')
0 files changed, 0 insertions, 0 deletions
