A footnote in the section describing <errno.h> says:
The macro errno need not be the identifier of an object. It might
expand to a modifiable lvalue resulting from a function call (for
example, *errno()).
Footnotes are non-normative, and this one is presumably intended to be informal, but that's not a valid macro definition for errno, both
because it's not fully protected by parentheses and because the function can't be named "errno".
Keith Thompson <Keith.S.Thompson+u@gmail.com> writes:
A footnote in the section describing <errno.h> says:
The macro errno need not be the identifier of an object. It might
expand to a modifiable lvalue resulting from a function call (for
example, *errno()).
Footnotes are non-normative, and this one is presumably intended to be
informal, but that's not a valid macro definition for errno, both
because it's not fully protected by parentheses and because the function
can't be named "errno".
I see no reason the function couldn't be named "errno".
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 457 |
Nodes: | 16 (2 / 14) |
Uptime: | 105:52:49 |
Calls: | 9,322 |
Calls today: | 2 |
Files: | 13,530 |
Messages: | 6,080,025 |