On Mon, 13 May 2019 at 18:42, Bill Igoe wrote:
>
> In a prop shop long ago , I also emailed all exception messages. It is a
> great way to correct logic errors and capture potentially sloppy code.
> Graphing the errors resulted in an exponential decline in errors.
>
> I also developed a handy per
You could do that with Log4j today ;-)
Gary
On Mon, May 13, 2019, 13:42 Bill Igoe wrote:
> In a prop shop long ago , I also emailed all exception messages. It is a
> great way to correct logic errors and capture potentially sloppy code.
> Graphing the errors resulted in an exponential decline
In a prop shop long ago , I also emailed all exception messages. It is a
great way to correct logic errors and capture potentially sloppy code.
Graphing the errors resulted in an exponential decline in errors.
I also developed a handy performance tracker for critical algorithms and
saved those re
Le 12/05/2019 à 14:25, Gary Gregory a écrit :
> +1 to removing email addresses from exception messages. We should do a pass
> over all of Commons.
+1, makes sense.
Emmanuel Bourg
-
To unsubscribe, e-mail: dev-unsubscr...@commons
+1 to removing email addresses from exception messages. We should do a pass
over all of Commons.
Gary
On Sun, May 12, 2019, 06:46 sebb wrote:
> Some of our code has Exception messages such as the following:
>
> >> (Collections:LRUMap)
> throw new IllegalStateException("Entry.before is null." +
> On May 12, 2019, at 6:45 AM, sebb wrote:
>
> Some of our code has Exception messages such as the following:
>
>>> (Collections:LRUMap)
> throw new IllegalStateException("Entry.before is null." +
> " Please check that your keys are immutable, and that you have used
> synchronization properly
Some of our code has Exception messages such as the following:
>> (Collections:LRUMap)
throw new IllegalStateException("Entry.before is null." +
" Please check that your keys are immutable, and that you have used
synchronization properly." +
" If so, then please report this to dev@commons.apache.o
