feat: add exit code support to sc_start and sc_stop - #152
Conversation
|
Looks very good to me. |
maehne
left a comment
There was a problem hiding this comment.
I expressed my doubts about this change to the LRM in this comment. Changing the signature of sc_start() may have unexpected effects on legacy code. At least add [[maybe_unused]] to the user-facing sc_start() functions.
The return value is intentionally not marked |
824286b to
0a42a11
Compare
|
Retargeted to |
Signed-off-by: Jan Henrik Weinstock <jan@mwa.re>
0a42a11 to
878f423
Compare
|
It was discussed in the LWG to include an update to Example 1 (multiple Example 2 (mixed with Which values should be returned in each case? We could say |
Hi all,
I though it could be useful to have and exit code that could be set using
sc_stopwhich would be returned bysc_start, e.g.:and then
Calling
sc_stop()without an argument is backward-compatible and equivalent tosc_stop(0). The implementation stores the exit code insc_simcontextandsc_startreturns it on exit.What do you think?