Getting Closure

(video)

8 Comments

  1. Oliver Burn
    Posted September 24, 2006 at 7:24 pm | Permalink

    Been playing with Ruby recently and liked the closures. Hope they add it to Java. Enjoyed your first Video blog, took me back to the 90’s. :-)

  2. Posted September 25, 2006 at 11:56 am | Permalink

    Why wait? Groovy has them now and compiles to byte code. You can write your closure logic in Groovy and call the Groovy classes from Java just like they were Java classes.

  3. Posted September 25, 2006 at 12:09 pm | Permalink

    Groovy Shmoovy, I want my increasing-complicated java. No, scratch that, I’m sick of updating the java grammar for Clover.

  4. Posted September 25, 2006 at 12:48 pm | Permalink

    The Blogger returns! Hurrah!

    The type inferencing aspects of the proposal are interesting. I suspect Java would be a better language with wide application of type inferencing.

    As for Groovy, I say, “Bah! Come back and talk to me if it ever reaches 1.0.”

  5. Posted September 27, 2006 at 12:08 am | Permalink

    Brilliant!

    You know, we can’t add methods to interfaces because it breaks backwards compatibility. But we can add new static methods to the JDK. I will be proposing adding a method to iterate over the entries in a map.

  6. Posted September 27, 2006 at 9:35 am | Permalink

    Glad you liked it Neal. Yeah, it did occur to me that the Map interface will never grow a forEachEntry() method, but I suppose it just seemed easier to have the example work that way :) And maybe I’ve been doing too much ruby lately…

  7. bmc
    Posted November 1, 2006 at 12:17 am | Permalink

    Great Harry Butler impersonation ;-) and nice to see web 2.0ish touch to your blog :-)

  8. Posted January 24, 2007 at 12:55 pm | Permalink

    Why use Java? Why not just use a language with closures and/or type inferencing? If you can whiz your way through the mess that is Java, then Haskell should be a breeze.

Post a Comment

Your email is never shared. Required fields are marked *

*
*