Re: [The Java Posse] Re: Java Has Always Had Closures

2011-09-13 Thread Josh Berry
My only problem with this, is to my knowledge we have invented the "pure closure" terminology. Again, this would be akin to my claiming that Java has had varargs since day one. You could always pass object arrays, after all. Nobody, to my knowledge, ever claimed those were the same thing. (I'm

[The Java Posse] Re: Java Has Always Had Closures

2011-09-13 Thread clay
>From the best I can gather, the principle disagreement is definitions. There are three views in this thread: A) Java has closures. Closures, by definition, do not necessarily require lambdas or first class functions, which Java doesn't have. B) Closures, by definition require lambdas and/or first

Re: [The Java Posse] Re: Java Has Always Had Closures

2011-09-13 Thread Josh Berry
On Tue, Sep 13, 2011 at 6:02 PM, Ricky Clarkson wrote: > It's myth-debunking time.  It's been so long since I had a good myth-debunk. I'm not sure what myth I was using that you debunked. :( The example I gave is a full closure where one wouldn't even realize a "lambda" was being used in most c

[The Java Posse] Re: Java Has Always Had Closures

2011-09-13 Thread opinali
JavaFX2 and GWT are exceptions to the rule, the vast majority of Java APIs/frameworks are not designed to benefit from intense use "closures" even in cases where such intense use would usually be a no-brainer design - remarkably collections (where are methods like collect, select, foreach etc.)

Re: [The Java Posse] Re: Java Has Always Had Closures

2011-09-13 Thread Ricky Clarkson
It's myth-debunking time. It's been so long since I had a good myth-debunk. You can't spot the closure in that Scala code because closures are not syntax. They are an implementation mechanism provided by compilers. The term we should have been using all these years is lambdas, which is what Has

Re: [The Java Posse] Re: Java Has Always Had Closures

2011-09-13 Thread Fabrizio Giudici
On 09/13/2011 07:28 PM, Josh Berry wrote: On Tue, Sep 13, 2011 at 12:49 PM, clay wrote: Ben + Josh, is this an accurate summary of your viewpoints: Java doesn't have true closures because of the "final" variable requirement and that any mutability of "closed" variables from the outer environmen

Re: [The Java Posse] Re: Java Has Always Had Closures

2011-09-13 Thread Kevin Wright
On 13 September 2011 16:31, clay wrote: > "This breaking news, just in: C has objects, and Lisp has static > types." > > Rather than all the snarky replies, how about you actually explain > what makes the Closure-like functionality in Java not really true > closures? > > I can articulate exactly

Re: [The Java Posse] Re: Java Has Always Had Closures

2011-09-13 Thread Josh Berry
On Tue, Sep 13, 2011 at 2:15 PM, clay wrote: > Regarding "pass by reference", most people will say Java passes > objects by reference, when it is more accurate to say that they pass > object references by value. I don't think there is much confusion or > debate on that issue. I think you'd be sur

[The Java Posse] The wave comes to Europe: Android smartphones passes iPhone in France

2011-09-13 Thread Fabrizio Giudici
http://www.lefigaro.fr/hightech/2011/09/13/01007-20110913ARTFIG00488-android-a-depasse-l-iphone-en-france.php -- Fabrizio Giudici - Java Architect, Project Manager Tidalwave s.a.s. - "We make Java work. Everywhere." java.net/blog/fabriziogiudici - www.tidalwave.it/people fabrizio.giud...@tidalwav

[The Java Posse] Re: Java Has Always Had Closures

2011-09-13 Thread clay
Regarding "pass by reference", most people will say Java passes objects by reference, when it is more accurate to say that they pass object references by value. I don't think there is much confusion or debate on that issue. With Closures, there is a lot of confusion. Java has something extremely c

Re: [The Java Posse] Re: Java Has Always Had Closures

2011-09-13 Thread Josh Berry
On Tue, Sep 13, 2011 at 12:49 PM, clay wrote: > Ben + Josh, is this an accurate summary of your viewpoints: Java > doesn't have true closures because of the "final" variable requirement > and that any mutability of "closed" variables from the outer > environment requires a level of indirection. >

[The Java Posse] JavaOne 2011

2011-09-13 Thread Takeshi Fukushima
Whos going to JavaOne this year? Do any of you have any tips to a first-timer (in both JavaOne and San Francisco)? -- http://mapsdev.blogspot.com/ Marcelo Takeshi Fukushima -- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this grou

[The Java Posse] Re: Java Has Always Had Closures

2011-09-13 Thread clay
Ben + Josh, is this an accurate summary of your viewpoints: Java doesn't have true closures because of the "final" variable requirement and that any mutability of "closed" variables from the outer environment requires a level of indirection. That's a logically consistent argument, although it's re

Re: [The Java Posse] Re: Java Has Always Had Closures

2011-09-13 Thread Ben Smith-Mannschott
On Tue, Sep 13, 2011 at 17:31, clay wrote: > "This breaking news, just in: C has objects, and Lisp has static > types." > > Rather than all the snarky replies, how about you actually explain > what makes the Closure-like functionality in Java not really true > closures? I'm not the O.P, but I'll

Re: [The Java Posse] Re: Java Has Always Had Closures

2011-09-13 Thread Josh Berry
On Tue, Sep 13, 2011 at 11:31 AM, clay wrote: > "This breaking news, just in: C has objects, and Lisp has static > types." > > Rather than all the snarky replies, how about you actually explain > what makes the Closure-like functionality in Java not really true > closures? I already did. Here, s

[The Java Posse] Re: Java Has Always Had Closures

2011-09-13 Thread clay
"This breaking news, just in: C has objects, and Lisp has static types." Rather than all the snarky replies, how about you actually explain what makes the Closure-like functionality in Java not really true closures? I can articulate exactly why C doesn't have real objects. You can do OO style pro

Re: [The Java Posse] Re: Java Has Always Had Closures

2011-09-13 Thread Sam Reid
The IntelliJ IDEA editor (9+) has a feature called "closure folding" for Java code that makes: Runnable r = new Runnable() { public void run() { System.out.println( "Hello" ); } }; display and read like: Runnable r = Runnable() { System.out.println( "Hello" ); }; With the "Runna

Re: [The Java Posse] Re: Java Has Always Had Closures

2011-09-13 Thread Russel Winder
On Tue, 2011-09-13 at 07:27 +0100, Kevin Wright wrote: > [ . . . ] > This breaking news, just in: C has objects, and Lisp has static types. > > More details to come as events unfold. > :-) Kevin, In reading the entries for this thread, I was at a loss as to where to dive in. Thanks for provid

[The Java Posse] Re: One Software Patent I'd Like To See Used

2011-09-13 Thread Casper Bang
My Samsung and LG TV's does this as well (the Sammy even comes with sound when you turn it off!). If you install CyanogenMod on your Android device, you can disable the sound. It's as if manufactures found out "Oh, this is a freakin' computer, let's hook into the lifecycle and do... something".

[The Java Posse] Invitation to connect on LinkedIn

2011-09-13 Thread Carl Jokl
I'd like to add you to my professional network on LinkedIn. - Carl Carl Jokl Researcher at University of Bradford Wakefield, United Kingdom Confirm that you know Carl Jokl: https://www.linkedin.com/e/-ywosys-gsiq6uh2-2p/isd/4185346978/5mTBoRYx/?hs=false&tok=2SMj8lpHMDFQU1 -- You are receiving I

Re: [The Java Posse] Re: Java Has Always Had Closures

2011-09-13 Thread Fabrizio Giudici
I won't dare to enter the ground of interpreting what's a closure because I'd get it wrong. But I think that the following statements are true: 1. "foobar" is a language construct that either is the same thing of a closure or a subset of a closure 2. foobars are useful for programmers 3. the

[The Java Posse] Re: One Software Patent I'd Like To See Used

2011-09-13 Thread Vince O'Sullivan
On Sep 12, 9:06 pm, Karsten Silz wrote: > On the Mac, there's a startup sound control... > ...not compatible with Lion. Damn! Guess what I've got. :) -- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to java