top | item 39742848

(no title)

subtra3t | 1 year 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".

discuss

Where 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|1 year ago

Good 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|1 year ago

Depends. Does Apple promise POSIX compliance for current macOS?

lxgr|1 year ago

I’m pretty sure they do, given that macOS is even still a Certified UNIX(tm).