Return-Path: Delivered-To: apmail-incubator-harmony-dev-archive@www.apache.org Received: (qmail 49688 invoked from network); 4 Oct 2006 10:14:40 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 4 Oct 2006 10:14:40 -0000 Received: (qmail 21933 invoked by uid 500); 4 Oct 2006 10:14:36 -0000 Delivered-To: apmail-incubator-harmony-dev-archive@incubator.apache.org Received: (qmail 21687 invoked by uid 500); 4 Oct 2006 10:14:35 -0000 Mailing-List: contact harmony-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: harmony-dev@incubator.apache.org Delivered-To: mailing list harmony-dev@incubator.apache.org Received: (qmail 21370 invoked by uid 99); 4 Oct 2006 10:14:34 -0000 Received: from idunn.apache.osuosl.org (HELO idunn.apache.osuosl.org) (140.211.166.84) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 04 Oct 2006 03:14:34 -0700 Authentication-Results: idunn.apache.osuosl.org header.from=alexey.v.varlamov@gmail.com; domainkeys=good X-ASF-Spam-Status: No, hits=0.5 required=5.0 tests=DNS_FROM_RFC_ABUSE DomainKey-Status: good X-DomainKeys: Ecelerity dk_validate implementing draft-delany-domainkeys-base-01 Received: from [66.249.82.238] ([66.249.82.238:5783] helo=wx-out-0506.google.com) by idunn.apache.osuosl.org (ecelerity 2.1.1.8 r(12930)) with ESMTP id C8/73-00170-C7983254 for ; Wed, 04 Oct 2006 03:14:27 -0700 Received: by wx-out-0506.google.com with SMTP id s13so137884wxc for ; Wed, 04 Oct 2006 03:13:24 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=ApQJ7wkWX/AjDs1JR5FwjpBmfYTahGuwhGmSEQGB5jtG01hufBQpeOKsgqk6CfDmd64mh87Afgmz4A/hfwkKiQBbb+AWwx93PbOVUmJcGiY5npne+Z+v+Kd1JmrBfddc3F9rInwMai8zF30CnbkGUdTMT8m/A/t2OSHBhnKRdQU= Received: by 10.70.36.9 with SMTP id j9mr746837wxj; Wed, 04 Oct 2006 03:13:24 -0700 (PDT) Received: by 10.70.23.14 with HTTP; Wed, 4 Oct 2006 03:13:24 -0700 (PDT) Message-ID: Date: Wed, 4 Oct 2006 17:13:24 +0700 From: "Alexey Varlamov" To: harmony-dev@incubator.apache.org Subject: Re: [r451637] - Code cleanup - ... - Remove unnecessary comments In-Reply-To: <3b3f27c60610031658l49fee490g5a5f80f60cd516c3@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <3b3f27c60610031658l49fee490g5a5f80f60cd516c3@mail.gmail.com> X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N 2006/10/4, Nathan Beyer : > If this is an event that should be logged, as the TODO indicated, then > why not just print out the stack trace and be done with it? If this > exception happens so often that you'd like it removed, then why would > we want to log a warning message, which I would presume would print to > the console just as frequently. Logging and printing to console essentially differ in flexible customization offered by the first approach. An application can have no console after all. We develop the common class library here, not an ordinary application - so let's not assume it will be used in some particular way. In this concrete case, stack trace is printed every time invalid input data is supplied - and it is normal for a unit test to cover some negative cases. But seeing console jammed with that rubbish is quite confusing (for me at least). OTOH, such info would be valuable for app developer - so why not satisfy both? > > As for TODOs, in general I find TODOs never get done, especially > trivial ones like this particular case. Because we have more priority tasks to be done. We just haven't reached that stage of completeness, when we can afford minor refining and polishing. Never say never, you know :) Please, announce ahead if you do such things in future. -- Regards, Alexey > > -Nathan > > On 10/3/06, Alexey Varlamov wrote: > > Nathan, > > > > I've seen you dropped many TODOs in "- Code cleanup -" series of commits; > > I'd like to know what reasoning was behind this? I think it's a bit > > early to erase TODOs without appropriate consideration... > > > > In particular, could you please undo the following change, it produces > > garbage messages during AUTH testing: > > > > modules/auth/src/main/java/common/org/apache/harmony/auth/login/DefaultConfigurationParser.java > > =========== > > @@ -216,12 +206,12 @@ public class DefaultConfigurationParser > > try { > > val = PolicyUtils.expand(st.sval, system); > > } catch (Exception e) { > > - //TODO: warning log > > - } > > + e.printStackTrace(); > > + } > > } > > > > -- > > WBR, > > Alexey > > > > --------------------------------------------------------------------- > > Terms of use : http://incubator.apache.org/harmony/mailing.html > > To unsubscribe, e-mail: harmony-dev-unsubscribe@incubator.apache.org > > For additional commands, e-mail: harmony-dev-help@incubator.apache.org > > > > > > --------------------------------------------------------------------- > Terms of use : http://incubator.apache.org/harmony/mailing.html > To unsubscribe, e-mail: harmony-dev-unsubscribe@incubator.apache.org > For additional commands, e-mail: harmony-dev-help@incubator.apache.org > > --------------------------------------------------------------------- Terms of use : http://incubator.apache.org/harmony/mailing.html To unsubscribe, e-mail: harmony-dev-unsubscribe@incubator.apache.org For additional commands, e-mail: harmony-dev-help@incubator.apache.org