FYI, JSR 334 has reached proposed final draft

[Neal Gafter]

One longstanding concern with the try-with-resource statement was the
software engineering implications of attempting to handle suppressed
exceptions - compared to other proposed mechanisms to handle them, there is
no obvious and scalable way with the currently proposed language construct
to organize programs to handle them (the only proposed code organization
techniques do not scale).  The response to this concern (since early coin
days) from the proponents of the current specification was we should
prototype the construct and see what patterns develop in code that uses the
construct, and then adjust the specification based on that experience.

That experience is necessary because it might not be possible to compatibly
address problems that experience may expose.  The developers associated with
project coin have no doubt written lots of new code using the feature and
reported their experience attempting to handle suppressed exceptions to the
jsr 224 mailing list, but we listeners on the coin list have unfortunately
not gained the benefit of that discussion.  The discussion shown publicly on
this list is insufficient in my mind to support an assumption that the
current mechanism has passed scrutiny from this point of view.  Therefore I
would ask the jsr 244 members to please summarize the relevant experience.

Cheers,
Neal

On Fri, Jun 24, 2011 at 3:37 PM, <joe.darcy at oracle.com> wrote:

> Hello.
>
> FYI, the proposed final draft specification of JSR 334 can now be
> downloaded from:
> http://jcp.org/aboutJava/communityprocess/pfd/jsr334/index.html
>
> -Joe
>
>