Open alashworth opened 5 years ago
Comment by syclik Tuesday Jul 08, 2014 at 14:17 GMT
"error" can be included for initialization errors, etc. that really are errors.
Comment by syclik Tuesday Jul 08, 2014 at 14:52 GMT
Places where I've found potentially problematic messages:
Comment by bob-carpenter Tuesday Jul 08, 2014 at 17:22 GMT
What's the context for all of these changes. Is this just not to freak people about for warnings that cause rejections?
Is the plan to have whatever's doing the catching and handling indicate severity of the "problem" or "issue"?
Comment by syclik Tuesday Aug 05, 2014 at 18:55 GMT
The context for changes:
Yes, I believe that we should indicate severity from the outside. I'm not sure how we would accomplish that, but that should be the goal. I don't think the underlying function calls should just deal with identifying an error and taking action.
I just swept threw all the functions and we've reduced the word "error" from our messages quite a bit. Here are the places where they still exist (I might have missed a few):
The action is to clean up these files and reword the messages, calling existing error-checking functions where appropriate.
Issue by syclik Tuesday Jul 08, 2014 at 14:15 GMT Originally opened as https://github.com/stan-dev/stan/issues/752
Messages from exceptions should not have the terms: