What steps will reproduce the problem?
1. Write an anonymous class, implementing a single-method interface, e.g.,
Runnable.
2. Stare at its code, find it slightly hard to read.
3. Wish Java had closures.
What is the expected output? What do you see instead?
Expected:
SwingUtilities.invokeLater({frame.setVisible(true);});
Actual:
SwingUtilities.invokeLater(new Runnable()
{
public void run()
{
frame.setVisible(true);
}
});
What version of the product are you using? On what operating system?
None, I'm reading the website.
Please provide any additional information below.
This is a planned feature for Eclipse and for IDEA - if coffee-bytes could
do it first, I'd use coffee-bytes. Other code folding I'm not so fond of,
as I like to see the code I'm working with (but not the excess).
Original issue reported on code.google.com by ricky.cl...@gmail.com on 25 Oct 2006 at 10:13
Original issue reported on code.google.com by
ricky.cl...@gmail.com
on 25 Oct 2006 at 10:13