Github user afs commented on the pull request:
https://github.com/apache/jena/pull/58#issuecomment-101213856
JENA-938
(using this PR to cover #60, #61, #62, #63)
Some of these are style points:
Unthrown checked exceptions: many (not all but most in my sampling) of
these are where the interface declaration has an exception but the code
implementation does not throw it currently.
Autogenerated code from an interface will include the exception declaration
and it is a right to have a later change and then throw the exception. This
will have an effect if the app code is using the implementing class, so when an
interface is part, not all, of a classes contract.
Unnecessary superinterface declarations: this is style - if inheriting from
a base class. it can be clearer to keep the "implement interface".
Needless typecasts: probably a left-over from converting to generics and
should be cleared. Or int/long conversion which also can be cleared up.
In all cases, a principle of "keep even if redundant to be clear" needs to
apply. (For me, the int/long cast conversion can fall into that category -
can't remember the rules at the time and probably won't next time I see the
code and certainly do not want accidiently truncation!)
Unused imports: my personal preference is no unused imports.
#58 also mentions unused variables (almost always should go IMO), unused
fields (almost always should go, occasional they are internal trackers like
stats.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
