<feed xmlns='http://www.w3.org/2005/Atom'>
<title>bjc-utils2.git/base/src/main/java/bjc/utils/exceptions/UnknownPragma.java, branch trunk</title>
<subtitle>Miscellaneous utilities and support code
</subtitle>
<link rel='alternate' type='text/html' href='https://git.ashardalon.com/bjc-utils2.git/'/>
<entry>
<title>Rename exceptions to not use Exception</title>
<updated>2020-10-06T23:26:52+00:00</updated>
<author>
<name>Ben Culkin</name>
<email>scorpress@gmail.com</email>
</author>
<published>2020-10-06T23:26:52+00:00</published>
<link rel='alternate' type='text/html' href='https://git.ashardalon.com/bjc-utils2.git/commit/?id=a7a87f682a039d4761112f1dedb9351f3d7a2bbf'/>
<id>a7a87f682a039d4761112f1dedb9351f3d7a2bbf</id>
<content type='text'>
This renames several of the stock exceptions to remove 'Exception' from
their name. This is something that I don't recall where I picked it up
from, but the idea is that the fact that it is an exception is generally
syntactically obvious. Therefore, you can instead give your exceptions
names which directly state what it wrong, as well as strongly implying
what you can do to fix it.

For instance, if you get a DirectionInvalid, it is apparent what the
issue is (it is less apparent why it is invalid, but that is another
issue, and a discussion for another time)</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
This renames several of the stock exceptions to remove 'Exception' from
their name. This is something that I don't recall where I picked it up
from, but the idea is that the fact that it is an exception is generally
syntactically obvious. Therefore, you can instead give your exceptions
names which directly state what it wrong, as well as strongly implying
what you can do to fix it.

For instance, if you get a DirectionInvalid, it is apparent what the
issue is (it is less apparent why it is invalid, but that is another
issue, and a discussion for another time)</pre>
</div>
</content>
</entry>
</feed>
