5 ms·
Amusingly, "losing stack trace information" is among the reasons the JVM doesn't do TCO -- it needs to keep it around for the security manager to do its thing.
by tsewlliw 14y ago
Amusingly, "losing stack trace information" is among the reasons the JVM doesn't do TCO -- it needs to keep it around for the security manager to do its thing. Its especially annoying there because references are held by higher stack frames and prevent GC, and the destructor excuse isn't present.
- happy_dino 14y ago> it needs to keep it around for the security manager to do its thing Haha. As if the JVM needed proper tail calls to get owned every other week. :-) Anyway, the discussion is pretty much moot, because "JVM" doesn't really refer to specific implementation. If one cares about proper tail calls, use an implementation which supports it.
- douglasisshiny 14y agoDoes the JVM get 'owned every other week'? Or are you thinking of the JRE?
- pjmlp 14y ago> Haha. As if the JVM needed proper tail calls to get owned every other week. :-) Correction, the JVM that is made available by Oracle, and most people wrongly think it is the only one. There are tons of JVM vendors out there.
- happy_dino 14y agoWhich I more or less already said with > If one cares about proper tail calls, use an implementation which supports it. Right?
- pjmlp 14y agoI would say yes, but your remark about getting owned is Oracle specific hence my comment.