Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!aioe.org!eternal-september.org!feeder.eternal-september.org!.POSTED!not-for-mail From: markspace <-@.> Newsgroups: comp.lang.java.programmer Subject: Re: ArrayList in Eclipse Date: Wed, 20 Apr 2011 20:01:32 -0700 Organization: A noiseless patient Spider Lines: 29 Message-ID: References: <919alnF872U1@mid.individual.net> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Injection-Date: Thu, 21 Apr 2011 03:01:37 +0000 (UTC) Injection-Info: mx02.eternal-september.org; posting-host="SuEAhE4Xkk16ijsXXUUVgQ"; logging-data="31918"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/G1m1ZGDiZ9xjCvwMgYC5p9eImvP/D1Zs=" User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9 In-Reply-To: <919alnF872U1@mid.individual.net> Cancel-Lock: sha1:/MQrVAr2kUSgIncFdGvuIp3CK0Q= Xref: x330-a1.tempe.blueboxinc.net comp.lang.java.programmer:3176 On 4/20/2011 5:05 PM, Dirk Bruere at NeoPax wrote: > I have an arraylist that I load with stuff when the app starts. > Is there any way I can check its contents in debug mode in an ongoing > basis? > If it's really an issue you might consider put a log statement with a log level of FINEST on that variable. If it's an issue now it's likely to be an issue at some point in the future. You strike me as new to Java, if not new to programming in general. This statement from the log4j page is interesting: > "Inserting log statements into your code is a low-tech method for debugging it. It may also be the only way because debuggers are not always available or applicable. This is often the case for distributed applications. "On the other hand, some people argue that log statements pollute source code and decrease legibility. (We believe that the contrary is true)." < 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.