[
https://issues.apache.org/jira/browse/SYSTEMML-620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15234464#comment-15234464
]
Matthias Boehm commented on SYSTEMML-620:
-----------------------------------------
yes, after the consolidation of LanguageException and ParseException, we should
rename it to DMLLanguageException (or DMLParseException) and make it a subclass
of DMLException. Btw, the old DMLParseException has already been deleted.
> Rename ParseException and/or subclass DMLException
> --------------------------------------------------
>
> Key: SYSTEMML-620
> URL: https://issues.apache.org/jira/browse/SYSTEMML-620
> Project: SystemML
> Issue Type: Task
> Components: Parser
> Reporter: Deron Eriksson
>
> Noted by [~freiss] WRT SYSTEMML-611:
> "If you're going to expose ParseException here, consider either renaming it
> to DMLParseException or making it a subclass of DMLException. Other systems
> and libraries use the name "ParseException", and we don't want users to have
> to type enter fully-qualified class names because they ended up with code
> that throws two kinds of "ParseException"."
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
