On Wed, May 4, 2016 at 5:46 AM, Fluid Dynamics <a2093...@trbvm.com> wrote:
> > Also, nothing you wrote addresses the other complaint I have, which is > that stuff shouldn't just magically stop working one day while it's sitting > in a drawer unused, and that there's not even an *excuse* for it to do so > if it's *software*. > I have heard a long history of issues where a program written to run on JVM 1.x does not work when run on JVM 1.y where y > x. While the byte code itself of the application should be portable to later JVM's, I believe that most or all of these compatibility issues are due to changes in the Java library. Your situation is quite similar to a case where you have an application that runs fine on Windows 7, but no longer runs correctly when you install Windows 10. The application did not change, but the Windows APIs it relies on likely did, in some way the application doesn't handle. Andy -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
