svn commit: r491668 - /jakarta/commons/proper/io/trunk/src/java/org/apache/commons/io/FileUtils.java

2007-01-01 Thread ggregory
Author: ggregory Date: Mon Jan 1 14:45:49 2007 New Revision: 491668 URL: http://svn.apache.org/viewvc?view=revrev=491668 Log: Add missing Javadoc tags. Use null is code format (codenull/code) Modified: jakarta/commons/proper/io/trunk/src/java/org/apache/commons/io/FileUtils.java Modified:

Re: [io] svn commit: r491668 - /jakarta/commons/proper/io/trunk/src/java/org/apache/commons/io/FileUtils.java

2007-01-01 Thread Stephen Colebourne
I'll be honest and say I dislike the convention of using code for null, as as such I'm not greatly enthused by this change. I'd prefer if no more files were changed. This comes down to my basic tenet that javadoc is for developers to read, and it is *frequently* read as source code, not as an

RE: [io] svn commit: r491668 - /jakarta/commons/proper/io/trunk/src/java/org/apache/commons/io/FileUtils.java

2007-01-01 Thread Gary Gregory
Hi All: Interesting and I do see your POV. IMO, it also depends on what tools you use do to your work. I use the Eclipse Javadoc view which presents the Javadoc comment in a formatted HTML view. I never bother to use the source of Javadocs to understand what the comments say as there usually is