--------------------------------------------------
From: "Ted Dunning" <ted.dunn...@gmail.com>
Sent: Friday, June 11, 2010 1:11 PM
To: "Commons Developers List" <dev@commons.apache.org>
Subject: Re: [Math] Help in debugging process
From a user's point of view logging is a waste of time if it doesn't tell
them something that they need/can take action on. Thus, I could see that
a
solve might log some hints about what to do when it detects a badly
ill-conditioned input, but I would be really not happy if it logs every
pivot value that it chooses. In general, things that work like java.math
should not log, especially if they throw exceptions anyway. Larger scale
systems could plausibly log, but I would be very dubious.
+1
Including logging in [math] has been discussed before (I don't have a
pointer, but searching the archives for this list should turn it up). Ted's
comment pretty much sums up the consensus. Of course, there is also the
very strong feeling that [math] should not have any required external
dependencies.
On Fri, Jun 11, 2010 at 12:21 PM, Roman Werpachowski <
roman.werpachow...@gmail.com> wrote:
Depends on the performance impact. I certainly wouldn't want to
discover that upgrading CM to new version made my code 20% slower
because the optimizer now logs stuff I'm not interested in.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
