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: | Amessyroom |
|---|---|
| Location: | Fayetteville, NC |
| Users: | 76 |
| Nodes: | 6 (0 / 6) |
| Uptime: | 54:00:04 |
| Calls: | 1,265 |
| Calls today: | 1 |
| Files: | 1,362 |
| D/L today: |
3 files (2,684K bytes) |
| Messages: | 285,448 |