right, C#. I didn't know, but should have guessed because C# introduced recursive tail-call optimization a long time ago under the influence of some Microsoft research folks who used to be involved with Haskell. I must admit I haven't looked at C# in a long time, but is C# really mainstraim ? ;-)
as for the Jena API, I guess it depends how far you want to go. Anywhere you use iterators today, you could introduce lambdas to express the operation on each element (this is the most immediate application). It will be interesting to see how far they go in the sdk itself because although much could be rewritten, Java developers are used to the concept of Iterators as well as anonymous classes. Having said this, the popularity of the syntactic 'for' introduced in Java 5 makes me think a rewrite (or rather extension) of any library with lambdas may become very popular. Time will tell Simon From: Rob Vesse <[email protected]> To: "[email protected]" <[email protected]>, Date: 01/21/2013 05:44 AM Subject: Re: Java6 end of life As the notional representative for .Net developers on this list I kinda feel insulted that you wouldn't consider C# which has had lambdas in the core language for 5 years now to be a mainstream language! ;-) I don't think lambdas necessarily require a rethink of the API, often they can be used to great effect to simplify code behind the scenes. Of course it depends how Java goes about adding lambdas, if they do it anything like .Net did then implementing certain interfaces automatically provides end users with the ability to apply lambdas with minimal effort on the part of the API developer. Rob On 1/17/13 7:46 PM, "Simon Helsen" <[email protected]> wrote: >ah yes, lambdas. Never thought I would see the day where I would be able >to use syntactic closures in a mainstream language. I am saying this as a >former functional language developer. (I never considered Smalltalk a >mainstream language, but to be fair it used to have blocks). I agree they >would be an opportunity to rethink the API > >Simon > > > > >From: >Damian Steer <[email protected]> >To: >[email protected], >Date: >01/17/2013 02:37 PM >Subject: >Re: Java6 end of life > > > > >On 17 Jan 2013, at 09:37, Andy Seaborne <[email protected]> >wrote: > >> FYI >> >> Java 6 end-of-life is approaching. >> >> End of public updates is next month (Feb 2013). >> End of public updates for Java7 is currently July 2014. >> Java8 is scheduled for Sept 2013 (and feature complete this month) >> >> Jena 2.10 is the next release. >> >> Thoughts on migration? > >We obviously hope people deploy jena on vendor supported java stacks, but >I don't see java 6 use falling rapidly. > >So are there other reasons to move? There are some reasonable useful >language changes, but nothing that compelling. For jena users I imagine >try with resources support would be great, and that (annoyingly) would >mean a change to 7 on our side (AutoCloseable is jdk 7+). > >Besides that the new nio stuff, particularly file paths, is great but not >especially relevant to jena. > >Java 8, otoh, is more significant. Lambdas might provide an opportunity >to >rethink the API. As I understand it some lambda support might not require >moving to java 8 -- simply accept single method interfaces and functions >will work -- but there's plenty of JDK changes that we might like to use. > >Damian > >
