I'm pretty certain that #include <errno.h> is the right way to do it everywhere. You can view, comment on, or merge this pull request online at:
https://github.com/OpenSmalltalk/opensmalltalk-vm/pull/179
-- Commit Summary --
* Update sqUnixExternalPrims.c
-- File Changes --
M platforms/unix/vm/sqUnixExternalPrims.c (6)
-- Patch Links --
https://github.com/OpenSmalltalk/opensmalltalk-vm/pull/179.patch https://github.com/OpenSmalltalk/opensmalltalk-vm/pull/179.diff
@aryler pushed 1 commit.
4254da4 Shouldn't need sys/errno.h if errno.h already #include'd
@aryler pushed 1 commit.
d7356df I think this should also be just errno.h, not sys/errno.h
It sounds correct, I verified `man errno` for freebsd, openbsd, linux and all mention `<errno.h>` I think it comes from macos, where `man errno` does not answer anything usefull... But where I get this answer to `man 2 intro`
**NAME** intro -- introduction to system calls and error numbers
**SYNOPSIS** #include <sys/errno.h>
**DESCRIPTION** This section provides an overview of the system calls, their error returns, and other common definitions and concepts.
MacOS seems to be the only one that specifies sys/errno.h in documentation. But if that were necessary then I suspect sys/errno.h would be found in more places in the codebase. Even in the MacOS dir there are plenty of plain errno.h's. Plain errno.h is POSIX. I'm pretty certain it's normal for errno.h to #include sys/errno.h.
Merged #179.
vm-dev@lists.squeakfoundation.org