Return-Path: X-Original-To: apmail-commons-dev-archive@www.apache.org Delivered-To: apmail-commons-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 391A37204 for ; Fri, 30 Sep 2011 18:29:16 +0000 (UTC) Received: (qmail 52804 invoked by uid 500); 30 Sep 2011 18:29:15 -0000 Delivered-To: apmail-commons-dev-archive@commons.apache.org Received: (qmail 52701 invoked by uid 500); 30 Sep 2011 18:29:15 -0000 Mailing-List: contact dev-help@commons.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Commons Developers List" Delivered-To: mailing list dev@commons.apache.org Received: (qmail 52693 invoked by uid 99); 30 Sep 2011 18:29:15 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 30 Sep 2011 18:29:15 +0000 X-ASF-Spam-Status: No, hits=-2.3 required=5.0 tests=RCVD_IN_DNSWL_MED,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [208.65.145.82] (HELO p02c12o149.mxlogic.net) (208.65.145.82) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 30 Sep 2011 18:29:08 +0000 Received: from unknown [198.6.208.103] (EHLO mail.sonalysts.com) by p02c12o149.mxlogic.net(mxl_mta-6.11.0-7) with ESMTP id f5a068e4.0.44357.00-337.104041.p02c12o149.mxlogic.net (envelope-from ); Fri, 30 Sep 2011 12:28:48 -0600 (MDT) X-MXL-Hash: 4e860a6007365042-db2fda9d7efce2c8710bf96ea8d885b2498136db From: "Gary Lucas" To: "'Commons Developers List'" References: <9be46e21-6fa9-48ff-9c1b-463fb0ea4b36@sonalysts.com> Subject: RE: [sanselan] Question about Java coding style for sanselan project Date: Fri, 30 Sep 2011 14:28:44 -0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable In-Reply-To: X-WatchGuard-IPS: message checked X-Spam: [F=0.2000000000; CM=0.500; S=0.200(2010122901)] X-MAIL-FROM: X-SOURCE-IP: [198.6.208.103] X-AnalysisOut: [v=1.0 c=1 a=1iE45vvKmsMA:10 a=fb5Wf9lGZMQA:10 a=BLceEmwcHo] X-AnalysisOut: [wA:10 a=IkcTkHD0fZMA:10 a=DjCRwU6BKXWGRozuCGhgpw==:17 a=pG] X-AnalysisOut: [LkceISAAAA:8 a=Ey13Ls4AAAAA:8 a=mV9VRH-2AAAA:8 a=ahJlmBsgA] X-AnalysisOut: [AAA:20 a=ST_jnFD8AAAA:20 a=Op31Vr4mAAAA:8 a=35boZU-QAAAA:8] X-AnalysisOut: [ a=JqEG_dyiAAAA:8 a=cKqcxGTpw4WYtCWJkpMA:9 a=90iuFD65GA9p1] X-AnalysisOut: [LNDnCQA:7 a=QEXdDO2ut3YA:10 a=PDCFtboiJeUA:10 a=dg9fIkVr2n] X-AnalysisOut: [EA:10 a=yaom3P4ADCAA:10 a=MSl-tDqOz04A:10 a=jYZ64_FAemcA:1] X-AnalysisOut: [0 a=88iI8knYSJUA:10] X-Virus-Checked: Checked by ClamAV on apache.org Gary, Thanks for the tip on the POM... I would have spent a lot of time = looking for that. I don't absolutely have to use generics, but it is kind of the way = things are trending these days. I'll wait and see what the community = has to say about it. g. -----Original Message----- From: Gary Gregory [mailto:garydgregory@gmail.com]=20 Sent: Friday, September 30, 2011 2:19 PM To: Commons Developers List Subject: Re: [sanselan] Question about Java coding style for sanselan = project Hello Gary(!): The project POM defines: 1.4 1.4 Java 1.4 is the current requirement. Using generics would mean bumping the requirements of the project to = Java 5. I do not know enough about the project to know if this is acceptable. = Seems OK to me though. I am not sure who on this ML knows this project well enough either, so = speak up ML. No revision comments. That's what SVN is for. Cheers, Gary On Fri, Sep 30, 2011 at 1:32 PM, Gary Lucas = wrote: > I am working on a couple of patches for sanselan. These involve about = > a couple of dozen files. I had two questions about coding style: > > First question: Is it okay to use generics for collections? These are = > a Java 1.5 element and I've noticed a couple of comments on the = project page > mentioning support for 1.4. I suspect that consideration is now = obsolete > since Java is now into version 1.7. > > Second question: Does anyone have preferences/guidelines for = including > "revision history" or "change log" information in the comments? At = the > present time, the sanselan code is practically without any comments at = > all, so I don't have any examples. I can see an argument for not=20 > including change log comments in a file because the subversion system=20 > maintains information about change histories. I can also see an=20 > argument for including them because a list of short, informative=20 > change notes at the top of a file can save a lot of time in the middle = > of a debugging session, especially in those times when one doesn't=20 > have access to the Internet > > Here's a strawman for a change log. I would put these in the code=20 > right below the Apache copyright information which appears at the top=20 > of all sanselan code files. > > > /*-------------------------------------------------------------------- > ----- > * > * Revision History: > * > * Date Name Description > * ------ --------- > --------------------------------------------------- > * --/---- Sanselan Sanselan 0.97 baseline (author unknown) > * 09/2011 G. Lucas Fix byte-order issue in double arrays for = EXIF > tags > > =20 > *--------------------------------------------------------------------- > ----- > * Notes: > > =20 > *--------------------------------------------------------------------- > ----- > */ > > > Computer Programming is the Art of the Possible Gary W. Lucas=20 > Sonalysts, Inc. > 215 Parkway North > Waterford, CT 06385 > 41-22-12.35 N / 72-10-07.54 W (USNG/MGRS: 18T YL 36787 83711) > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org > For additional commands, e-mail: dev-help@commons.apache.org > > -- E-Mail: garydgregory@gmail.com | ggregory@apache.org JUnit in Action, = 2nd Ed: http://bit.ly/ECvg0 Spring Batch in Action: http://bit.ly/bqpbCK Blog: http://garygregory.wordpress.com Home: http://garygregory.com/ Tweet! http://twitter.com/GaryGregory --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org For additional commands, e-mail: dev-help@commons.apache.org