I was expecting errno inside the messenger to be reset to 0 at the end of any
successful API call.
It isn't: instead it looks like the idea is that errno preserves the most
recent error that happened, regardless of how long ago that might be.
Is this intentional?
I am having a hard time
No, you're right.
errno is never set to zero by any system call or library function
( That's from Linux doco. )
OK, I was just philosophically challenged.
I think what confused me was the line in the current Proton C doc (about errno)
that says an error code or zero if there is no
On Mon, Sep 16, 2013 at 12:33:29PM -0400, Hiram Chirino wrote:
Do other APIs reset the errno? I could have sworn they didn't.
Successful system calls and library functions never reset errno to 0, so
this variable may have a nonzero value as a consequence of an error from
a previous call.
Do other APIs reset the errno? I could have sworn they didn't.
On Mon, Sep 16, 2013 at 12:01 PM, Michael Goulish mgoul...@redhat.com wrote:
I was expecting errno inside the messenger to be reset to 0 at the end of any
successful API call.
It isn't: instead it looks like the idea is that
