> > John Birrel writes:
> > >extern  int *__error();
> > >#define errno (*__error())
>
> The question is, is this safe in other
> cases, and do POSIX or other standards allow errno to be a macro?

In fact, the draft POSIX 1003.1c (threads extension) contains a copy of the
above code, albeit with the lines reversed (2.4.1, pages 17 & 18 in draft 10).
Maybe, John fetched it from there?
--
ws@TooLs.DE     (Wolfgang Solfrank, TooLs GmbH) 	+49-228-985800