🚀 go-pugleaf

Dan Pop (danpop@mail.cern.ch) wrote:
: >> However, errno is an lvalue, and the object designated by this lvalue
: >> is definitely accessible.
: >
: >But "the object" may be a different object at a different time.
: >
: Even if it is a different object at a different time, this should be
: transparent to a conforming program.  Consider this example:

: #imclude <errno.h>
: #include <stdlib.h>

: void blah(int i)
: { 
:     errno = i;
: }

: int main(void)
: {
:     int i = 3;
:     blah(i);
:     if (i == errno) return EXIT_SUCCESS;
:     return EXIT_FAILURE;
: }

: Is this code allowed to return an unsuccessful termination status to
: the host environment?

I would agreee that the intent on ISO C 7.1.4 (as given in Plauger) is
that errno is a single value, however I would say that on a strict
reading that is not assured. Also nothing is said except in footnotes
about  applications setting errno. The mention is in footnote 93 where
it only talkes about setting it to zero, so strictly assigning anything
other than zero could have undefined or implementation specific
behaviour. The wording of this section could be improved.

--
Stephen Baynes                              baynes@mulsoc2.serigate.philips.nl
Philips Semiconductors Ltd
Southampton                                 My views are my own.
United Kingdom