I look forward to being corrected, but all the examples I've seen of lambaj show things like:
forEach(someCollection).setSomeMethod(withThis); Giving to mind that forEach() returns some dynamic proxy to someCollection that iterates over it, calling the provided method, which is great for somethings, but in almost 99% of the times I've wanted a nice closure based syntax for this, I've wanted to call multiple statements on each item, or refer to the 'each' as part of that statement, such like: someCollection.forEach(each => each.value = each.value * 2); Unless theres something akin to how Mockito handles parameters I don't see how they're comparable, does lambaj allow for something like: forEach(someCollection).setEach(each().getValue() * 2) with each() return a ThreadLocal bound value from each iteration? -- Pull me down under... On Sat, Nov 21, 2009 at 12:10 PM, Mario Fusco <mario.fu...@gmail.com> wrote: > Maybe I am a bit biased, but to be honest I don't see big differences > between what I developed in my project ( http://code.google.com/p/lambdaj > ) and what this spec should make available in about a year (except a > nicer syntax of course). 2 years of discussions plus 1 year of delay > in the jdk7 release sounds a bit too much to have a so small set of > features. -- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to javapo...@googlegroups.com. To unsubscribe from this group, send email to javaposse+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/javaposse?hl=.
