Re: [bcel] console logging

2016-06-11 Thread Benedikt Ritter
No logging via System.out/err. Either use a decent logging framework or use exceptions to propagate errors. I'm in the throw exceptions camp. Benedikt Gary Gregory schrieb am Sa., 11. Juni 2016 um 01:15: > I see this in [bcel]: > > System.out.println(buf.toString()); > e

Re: [bcel] console logging

2016-06-10 Thread sebb
On 11 June 2016 at 01:41, Gary Gregory wrote: > On Fri, Jun 10, 2016 at 4:33 PM, sebb wrote: > >> On 11 June 2016 at 00:15, Gary Gregory wrote: >> > I see this in [bcel]: >> > >> > System.out.println(buf.toString()); >> > e.printStackTrace(); >> > >> > Should that be left

Re: [bcel] console logging

2016-06-10 Thread Gary Gregory
On Fri, Jun 10, 2016 at 4:33 PM, sebb wrote: > On 11 June 2016 at 00:15, Gary Gregory wrote: > > I see this in [bcel]: > > > > System.out.println(buf.toString()); > > e.printStackTrace(); > > > > Should that be left in there or removed? > > Where is it? > org.apache.bcel

Re: [bcel] console logging

2016-06-10 Thread sebb
On 11 June 2016 at 00:15, Gary Gregory wrote: > I see this in [bcel]: > > System.out.println(buf.toString()); > e.printStackTrace(); > > Should that be left in there or removed? Where is it? > Gary > > -- > E-Mail: garydgreg...@gmail.com | ggreg...@apache.org > Java Persi

[bcel] console logging

2016-06-10 Thread Gary Gregory
I see this in [bcel]: System.out.println(buf.toString()); e.printStackTrace(); Should that be left in there or removed? Gary -- E-Mail: garydgreg...@gmail.com | ggreg...@apache.org Java Persistence with Hibernate, Second Edition JUnit in