commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gilles (JIRA)" <j...@apache.org>
Subject [jira] Commented: (MATH-361) Localization and Error Handling
Date Mon, 28 Jun 2010 13:17:51 GMT

    [ https://issues.apache.org/jira/browse/MATH-361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12883139#action_12883139
] 

Gilles commented on MATH-361:
-----------------------------

{quote}
I don't think it makes sense to argue about who the exception messages are for [...]
{quote}

I think the opposite, because it has an impact on the library design.
Not that CM cannot go on with the current way; but my point is that Luc and you are focusing
on top-level users while stressing that CM in a low-level component. To me, that is a blatant
contradiction that produces drawbacks which I presented in several usage examples (which you
didn't address), while you always reply with a single use case where the user is yourself
(i.e. a CM developer). Anyone else who is using a high-level application based on CM will
be baffled by the "detailed exception message" because, in all but the most trivial case,
his actions will have only a remote connection to the exception triggered by CM.
I'm pinpointing at a minute detail of the design of CM, explaining that it can come in the
way of some direct users of CM. The current long list of errors is in fact imposing your view
(of what is important) to future application developers. [As an example, let's say that someone
wants to create a GUI (e.g. for the statistician referred to above), he will want to define
his own detailed error messages to be displayed in the GUI with a formatting of his choice.
The statistician will never see the messages created by CM.]
If a CM exception (resulting from a precondition violation) reaches the end-user level, it
means there was some unanticipated problem in the call chain. And to correct it, one would
need more than just the "detailed message": the end-user will pass the stack trace to the
application developer, who will correct a possible bug in his code (such as a missing check
of a precondition) or pass it on the the CM developers.


> Localization and Error Handling
> -------------------------------
>
>                 Key: MATH-361
>                 URL: https://issues.apache.org/jira/browse/MATH-361
>             Project: Commons Math
>          Issue Type: Improvement
>    Affects Versions: 2.1
>            Reporter: Gilles
>            Priority: Minor
>         Attachments: l10n.tar.gz, res.tar.gz
>
>
> This proposal aims at easing the handling of error during algorithms development, and
also enhancing the flexibility of the error reporting (provide meaningful exception classes
and run-time selection of the localization formatting).
> More details at [http://www.mail-archive.com/dev@commons.apache.org/msg14570.html]

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message