Comments on: Java Code Style and some Handy Plugins for Eclipse http://www.stephendowney.net/blog/2007/01/12/java-code-style-and-some-handy-plugins-for-eclipse/ Thu, 17 Sep 2009 22:18:35 -0500 http://wordpress.org/?v=2.8.6 hourly 1 By: Stephen Downey http://www.stephendowney.net/blog/2007/01/12/java-code-style-and-some-handy-plugins-for-eclipse/comment-page-1/#comment-35518 Stephen Downey Tue, 10 Feb 2009 21:28:02 +0000 http://www.stephendowney.net/blog/2007/01/12/java-code-style-and-some-handy-plugins-for-eclipse/#comment-35518 Hey "Fred Coder", Thanks for your feedback, I appreciate your view, however I would tend to disagree with you about redundant braces. I think these are a necessity in coding and help to provide clean consistent code that can be easily picked up and followed. Hey “Fred Coder”,
Thanks for your feedback, I appreciate your view, however I would tend to disagree with you about redundant braces.

I think these are a necessity in coding and help to provide clean consistent code that can be easily picked up and followed.

]]> By: Fred Coder http://www.stephendowney.net/blog/2007/01/12/java-code-style-and-some-handy-plugins-for-eclipse/comment-page-1/#comment-35514 Fred Coder Mon, 09 Feb 2009 23:39:31 +0000 http://www.stephendowney.net/blog/2007/01/12/java-code-style-and-some-handy-plugins-for-eclipse/#comment-35514 I think you need a better example... This statement: if (testBoolean) myNum++; is concise and clear as a bell. I can't imagine anyone being confused as to whether the if statement applies to following code. The following code will NOT be indented, and neither is there an opening brace. (Its even more clear if you adopt a style that has opening braces always on the next line from an if/for/etc) Putting in redundant braces simply clutters up the code and makes it harder to navigate through quickly. I think you need a better example… This statement:
if (testBoolean) myNum++;

is concise and clear as a bell. I can’t imagine anyone being confused as to whether the if statement applies to following code. The following code will NOT be indented, and neither is there an opening brace. (Its even more clear if you adopt a style that has opening braces always on the next line from an if/for/etc)

Putting in redundant braces simply clutters up the code and makes it harder to navigate through quickly.

]]> By: Stephen Downey http://www.stephendowney.net/blog/2007/01/12/java-code-style-and-some-handy-plugins-for-eclipse/comment-page-1/#comment-10588 Stephen Downey Fri, 12 Jan 2007 11:45:49 +0000 http://www.stephendowney.net/blog/2007/01/12/java-code-style-and-some-handy-plugins-for-eclipse/#comment-10588 Paul, I haven't tried Coverlipse yet, just came across it in the article above but it would be good to get a code coverage tool. Have you stopped developing No-unit, if not would you try to build an Eclipse plugin for it? It would be a good way to get your tool to a lot of developers. Stephen Paul,

I haven’t tried Coverlipse yet, just came across it in the article above but it would be good to get a code coverage tool.

Have you stopped developing No-unit, if not would you try to build an Eclipse plugin for it? It would be a good way to get your tool to a lot of developers.

Stephen

]]> By: Paul Browne - TIPE http://www.stephendowney.net/blog/2007/01/12/java-code-style-and-some-handy-plugins-for-eclipse/comment-page-1/#comment-10587 Paul Browne - TIPE Fri, 12 Jan 2007 11:14:32 +0000 http://www.stephendowney.net/blog/2007/01/12/java-code-style-and-some-handy-plugins-for-eclipse/#comment-10587 Stephen, Good to see that you're using coverlipse. We had a similar (open source) project called <a href="http://www.firstpartners.net/blog/category/nounit/" rel="nofollow">NoUnit</a> on the go - still usable but Coverlipse probably has the edge (with Eclipse integration). Paul Stephen,

Good to see that you’re using coverlipse. We had a similar (open source) project called NoUnit on the go – still usable but Coverlipse probably has the edge (with Eclipse integration).

Paul

]]>