Why some java methods in core libraries end with numbers?

Issue

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.

Solution

It is just a convention to deal with cases where you have a public API method and a corresponding private method. There is no mention of this in the original Java Style Guide.

I think the history of this convention predates Java. I vaguely recall seeing it in C libraries in 4.x BSD Unix. That was the mid 1980's.

Answered By - Stephen C