Re:It's time to get the Posix elephant off our necks
by cvccvroomvroom on Wednesday February 22, 2023 @07:30PM
(#34905165)
Maybe it was written as a parody and we just don't get the joke? (Not POSIX, the article. POSIX survives fine outside of UNIX in embedded systems and somewhat on Mac OS and Windows.)
[ Parent
| on HN ]
Re:It's time to get the Posix elephant off our necks
by olliej on Wednesday February 22, 2023 @08:46PM
(#34905715)
macOS at least is definitely posix compliant - not just somewhat. It was a big part of what was needed for xserves to be competitive (alas being shiny and aluminium was not :) ). While xserves have died, macOS remains entirely posix compliant - complete with the horrific %n format specifier (although an environment variable is needed for it to be respected in non read only format strings iirc)
Re:It's time to get the Posix elephant off our necks
by kevin_thibedeau on Wednesday February 22, 2023 @10:54PM
(#34906556)
%n isn't from POSIX. It has always been taken from the ANSI draft.
Re:It's time to get the Posix elephant off our necks
by amiga386 on Thursday February 23, 2023 @12:34AM
(#34907144)
It's arguable that macOS is actually POSIX compliant. I was frustrated that poll() simply refused to work on terminal devices in Mac OS X 10.1 and I had to use select() instead. And it's still not supported in macOS 13!
Can you claim POSIX compliance while actually not complying, by saying "BUG: currently doesn't comply" for more than 20 years?
https://developer.apple.com/library/archive/documentation/Sy...
> BUGS > The poll() system call currently does not support devices.
https://pubs.opengroup.org/onlinepubs/9699919799/functions/p...
> The poll() function shall support regular files, terminal and pseudo-terminal devices, FIFOs, pipes, sockets and STREAMS-based files.
Re:It's time to get the Posix elephant off our necks
by saagarjha on Thursday February 23, 2023 @02:50AM
(#34907996)
There are no environment variables to disable this behavior.