kirk wrote: > Jon Harrop wrote: > >> On Thursday 02 April 2009 15:09:12 Charles Oliver Nutter wrote: >> >> >>> It's not necessarily Sun's choice when it exhibits external behavioral >>> changes. Such changes must be standardized so all JVMs will support >>> them. If it were just up to Sun, it would probably go in (since I know I >>> want it and several others want it). >>> >>> >> Ok. I only care about Sun's JVM because it is the defacto standard. If tail >> calls are not adopted as a standard across all JVMs, what are the odds of >> Sun >> including them just in its own JVM as an extension? >> >> > why do they have to be exposed? Isn't tail recursion and implementation > detail? And an optimization at that? > No, tail recursion is not an implementation detail, since some programs become valid with it that isn't valid without it. As such, there is a real functional difference. It isn't very noticeable for the programs written using the Java language, but other languages want to expose this functionality.
Cheers -- Ola Bini (http://olabini.com) Ioke creator (http://ioke.org) JRuby Core Developer (http://jruby.org) Developer, ThoughtWorks Studios (http://studios.thoughtworks.com) Practical JRuby on Rails (http://apress.com/book/view/9781590598818) "Yields falsehood when quined" yields falsehood when quined. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "JVM Languages" group. To post to this group, send email to jvm-languages@googlegroups.com To unsubscribe from this group, send email to jvm-languages+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/jvm-languages?hl=en -~----------~----~----~----~------~----~------~--~---
