naming conventions - Why some java methods in core libraries end with numbers?

Question

It's common in a lot of classes in JDK, just a few examples:

1. java.util.Properties
   • load0
   • store0
2. java.lang.Thread
   • start0
   • stop0
   • setPriority0

Usually they are private native methods (like in Thread class), but sometimes they are just private (Properties class)

I'm just curious if anybody know if there is any history behind that.

Answer 1

I believe they are named like that because equivalent functions with same names exist in the code and just to distinguish between native helper functions and public functions they decided to suffix them with 0.

in java.util.Properties both load, store and load0, store0 exist.