I suppose it's for someTrickyCode(); // This code is tricky -> // This code is tricky someTrickyCode(); I prefer the latter style, since you know that no matter how longer the trickyCodeLine gets, you will still be able to see the comment. So the intention is quite helpful for me.
I had the same thought when this was suggested, but now that I have it (and have it working), I find I use it quite a bit. Putting comments on the line before rather than trailing after just seems clearer to me, and makes for tidier layout. If it doesn't cost much to move it (like just a quick Alt-Enter), I find I do it quite often.
At some point, usability consists of filing keystrokes off of operations that would be common and valuable if they didn't take so many keystrokes. Very prospective and liable to make mistakes, but in this case I think value was found.
I suppose it's for
someTrickyCode(); // This code is tricky
->
// This code is tricky
someTrickyCode();
I prefer the latter style, since you know that no matter how longer the
trickyCodeLine gets, you will still be able to see the comment. So the
intention is quite helpful for me.
R
I also prefer the latter style, but that intention occured also at my
class comments:
/**
@author Tom
*/
public class Foo {
}
Tom
I had the same thought when this was suggested, but now that I have it (and have it working), I find I use it quite a bit. Putting comments on the line before rather than trailing after just seems clearer to me, and makes for tidier layout. If it doesn't cost much to move it (like just a quick Alt-Enter), I find I do it quite often.
At some point, usability consists of filing keystrokes off of operations that would be common and valuable if they didn't take so many keystrokes. Very prospective and liable to make mistakes, but in this case I think value was found.
--Dave Griffith
That's a bug, which is fixed in the next release.
--Dave Griffith