#nevet

07:40 jreicher Chronos: because it's the JVM "implementing" that exit code. If it wanted, it could override any exit code written in the Java code it's running.
11:43 Chronos jreicher: Ah, that makes sense. Your carefully crafted exit code could easily be overridden, so you can't count on it.
11:51 dreamreal but that's the case for any of them
11:54 dreamreal including C
11:59 dreamreal the only way you're going to guarantee that sort of thing is at the language spec level, and you have to trust the spec for it to be true anyway
12:19 jreicher I was thinking that, and realised I never looked at the Java language spec for this.
12:20 jreicher https://docs.oracle.com/javase/specs/jls/se25/html/jls-12.html#jls-12.8
12:20 nevet Chapter 12. Execution
12:28 dreamreal jreicher: https://docs.oracle.com/en/java/javase/25/docs/api/java.base/java/lang/System.html#exit(int) is more important for this
12:28 nevet System (Java SE 25 & JDK 25)
12:29 dreamreal And, of course, https://docs.oracle.com/en/java/javase/25/docs/api/java.base/java/lang/Runtime.html
12:29 nevet Runtime (Java SE 25 & JDK 25)
12:31 jreicher Those two are actually referred to explicitly in the language spec section I linked
12:32 dreamreal yes, but you'd have to follow them links!!!
12:32 dreamreal !!11!
12:33 jreicher :)