[
https://issues.apache.org/jira/browse/IMAGING-154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16352290#comment-16352290
]
Gilles commented on IMAGING-154:
--------------------------------
Hi Bruno.
Was there a discussion about this that concluded to a "simple" removal?
Just quickly browsing through the changes, it seems (?) that obtaining debug
info requires either access to the internals or, for example, implementing
bit-masking gymnastics (which is tedious and error-prone).
Input to this library's code is not only through passing known parameters
(args to method) but also reading "external" data (image file); so I guess that
in some cases of malformed (or unknown) input, logging is an immense help.
A flexible alternative to the current "dump" is to use a logging interface
such as provided by
[Log4J2|http://logging.apache.org/log4j/2.x/manual/api.html].
> Remove Debug class
> ------------------
>
> Key: IMAGING-154
> URL: https://issues.apache.org/jira/browse/IMAGING-154
> Project: Commons Imaging
> Issue Type: Task
> Affects Versions: Patch Needed
> Reporter: Benedikt Ritter
> Assignee: Bruno P. Kinoshita
> Priority: Major
> Fix For: 1.0
>
>
> Low level libraries should not do logging, but communicate through the use of
> exceptions and meaningful return values. Remove the Debug class and all it's
> uses.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
