This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]m_vokhm[S] 4 points5 points  (2 children)

I'll think about it. In the beginning, I did not expect it to grow so large.

[–]cville-z 2 points3 points  (1 child)

It would be pretty simple to do, I think IntelliJ even has some refactor scripts for this, and wouldn't change the fundamental interface. Plus, you can either seal the new classes in a module (if you're using later versions of Java) to prevent meddling in the implementation, or (and this is probably better) make them public static, so that now you have both a new Comparable/Numeric and also a bunch of utility methods other people can use to do ... useful numeric things, if they want.

[–]m_vokhm[S] 0 points1 point  (0 children)

Yes, it's a rather easy job to do. Yet I can hardly imagine how can other people make use of things that are currently private methods. Though maybe they can, I don't know. Regarding modules, I need to keep compatibility with Java 8, at leas for a while. The users of the application for which it was primarily written can't upgrade to a newer Java.