7 ms·
> Seems similar to the JVM situation Oracle was relying on behaviour that was POSIX valid so I don't see how it is "incorrect code".
by subtra3t 3y ago
> Seems similar to the JVM situation
Oracle was relying on behaviour that was POSIX valid so I don't see how it is "incorrect code".
- jjtheblunt 2y agoWhere did you get that it’s posix valid? Like link to posix spec? Or hearsay? I know what you mean but haven’t found such. (SIGTERM is catchable though so it does seem a bug/overkill sending SIGKILL instead of SIGSEGV or even SIGTERM.)
- subtra3t 2y agoGood catch. I haven't found a proper source other than a quotation from some HN comment, so I'm not sure if it actually is POSIX valid or not, just that many people seem to think it is.
- bzzzt 2y agoDepends. Does Apple promise POSIX compliance for current macOS?
- lxgr 2y agoI’m pretty sure they do, given that macOS is even still a Certified UNIX(tm).