Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!aioe.org!.POSTED!not-for-mail From: "Nasser M. Abbasi" Newsgroups: comp.lang.java.programmer Subject: Re: ArrayList in Eclipse Date: Wed, 20 Apr 2011 21:21:05 -0700 Organization: Aioe.org NNTP Server Lines: 30 Message-ID: References: <919alnF872U1@mid.individual.net> Reply-To: nma@12000.org NNTP-Posting-Host: tUYQ4Ty9mMw9Pdc8TJRFQA.user.speranza.aioe.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: abuse@aioe.org User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9 X-Notice: Filtered by postfilter v. 0.8.2 Xref: x330-a1.tempe.blueboxinc.net comp.lang.java.programmer:3177 On 4/20/2011 8:01 PM, markspace wrote: > > I've also found that well placed log statements are a faster way of > debugging than stepping through code in a debugger. And debuggers can't > be used when timing is a source of error. > > > It depends on the situation. In some cases, log debugging is much more productive. Sometimes, one want to set a breakpoint somewhere and examine data in a way not easily done by logging. One problem with log debugging is how to turn it on/off on selected area of the applications. If one wants logging generated from one function and not another, then one ends up using more flag and switches. Also there can be a need to change the level of debugging (verbose, summary, etc...) But I think a well designed logging facility can achieve most of this, but I think this needs to be designed and developed as part of the whole application. For large applications, a good logging facility is essential. I think some programmers add logging after the application is deveopled, instead of designing it as part of the application itself. --Nasser