InfoQ

InfoQ

News

My Bookmarks

Login or Register to enable bookmarks for unlimited time.

The content has been bookmarked!

There was an error bookmarking this content! Please retry.

Java Closure Proposals Compared, JCA Position Paper Announced

Posted by Rob Thornton on Apr 13, 2007

Sections
Development,
Architecture & Design
Topics
JCP Standards ,
Programming ,
Java
Tags
Closures

Howard Lovatt, the author of the C3S proposal for closures in Java, has written a detailed comparison of the four best known proposals (C3S, FCM, CICE, and BGGA). At the same time the authors of the FCM proposal have released a new position paper building on FCM for control abstraction. Ricky Clarkson thinks that CICE is insufficient and wonders if internal politics at Google are affecting it.

Lovatt walks through the four proposals and compares each in terms of eleven features:

  1. Short syntax for the creation of an instance of an inner class/closure
  2. Access to both this pointers and methods within an inner class
  3. More than one method in an inner class/closure instance
  4. Implementation of methods defined in classes
  5. Type inference
  6. Method, constructor, and field literals
  7. Short syntax (particularly for control structures and short methods)
  8. Assignment to local variables and no final requirement
  9. Variable number of exceptions
  10. Method/function types (with shorter syntax)
  11. Non-local, return, break, and continue

His goal in writing is to separate out the inner class / closure part of the proposal from any other extras that might come with it. On the heels of this comparison, Stephen Colebourne, Stefan Schulz, and Ricky Clarkson have built upon FCM with a position paper (they clarify that it is not a proposal and thus not complete) for Java Control Abstraction. They motivate the need for JCA because there are places closures are not applicable. Such a place is where an API exists that is used very similarly to a built in keyword.

Lastly, Ricky Clarkson wonders if politics at Google have affected the advancement of BGGA proposal. There are restrictions on who is able to contribute to the JCP, specifically if your employer is a member, you cannot be. Clarkson suggests that Josh Bloch, Google's contact on the JCP, may be uninterested in creating a JSR for as he has already proposed CICE. Bob Lee, one of the co-authors of CICE responds to Clarkson saying this is an unfair suggestion and that there is no rush to get closures into Java.

Clarkson by Ricky Clarkson Posted
  1. Back to top

    Clarkson

    by Ricky Clarkson

    That's the first time I've been called Clarkson since school.

    Josh Bloch recently replied to a blog post somewhere to remind us of his solution to many of the use cases that CICE alone misses out on - docs.google.com/View?docid=dffxznxr_1nmsqkz - I still think with CICE and ARM blocks he's likely to miss some use cases, but I haven't identified any yet.

    Cheers.

Educational Content

New-age Transactional Systems - Not Your Grandpa's OLTP

John Hugg discusses high volume transaction processing applications with high and low frequency profiles, and how VoltDB can be used for that purpose.

Cool Code

Kevlin Henney examines code samples to see what can be learned from them starting from the premise that one won’t write great code unless he knows how to read it.

Collaboration: At the Extremities of Extreme

Jason Ayers share the observations he made watching a team of developers collaborating in real time on the same code base, pushing XP, pair programming and continuous integration to their extremes.

Yesod Web Framework

Michael Snoyman presents Yesod, a web framework written in Haskell and containing a web server, templating, ORM, libraries (templating, gravatar, etc.).

Transactions without Transactions

Richard Kreuter and Kyle Banker on how to avoid classical RDBMS transactional systems by using compensation mechanisms, transactional messaging or transactional procedures.

Attila Szegedi on JVM and GC Performance Tuning at Twitter

Attila Szegedi talks about performance tuning Java and Scala programs at Twitter: how to approach GC problems, the importance of asynchronous I/O, when to use MySQL/Cassandra/Redis, and much more.

10 tips on how to prevent business value risk

One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.

Interview: Software Systems Architecture: Working With Stakeholders Using Viewpoints and Perspectives

InfoQ spoke to the authors of Software Systems Architecture on a couple of new topics, the System Context viewpoint and Agile, which have been added to the second edition.