Class declarations and object modeling: Correct Solution

Translate the specification below into an idiomatic Java class definition.

(In this context, "idiomatic" means following the common style and conventions of the language.)

1. One kind of thing that exists in our model is a Litriac.

2. All Litriacs share a single oinsu, which is an int. No other classes can directly ask for the value of oinsu. The value of oinsu starts out as 3 when the program starts. Every time a new Litriac is created, it adds 2 to oinsu.

Solution

public class Litriac {
    public static int oinsu;

    public Litriac() {
        oinsu += 2;
    }

    public static void onStart() {
        oinsu = 3;
    }
}

Things to check in your solution:

• Is every public and private modifier correct?
• Are the correct items static?
• Are the correct items final?
• Are all the variable types and method return types correct?
• Are the class members in the correct order? It should be: (1) static variables, (2) instance variables, (3) constructors, (4) methods.
• Do members have the correct capitalization?

Acceptable variations in the solution:

• It is OK if you initialized non-static variables in the constructor instead of in the declaration. (Ask your instructor if you aren’t clear what this means.) Note that static variables must be initialized in the declaration.
• It is OK if you used a slightly different but equivalent form of an expression, such as += 1 instead of ++.

Related puzzles:

• Static and runtime types: Correct Solution (wtmg-rjtd-9pkv-ixwu)
• Stack frames and objects (like the Idea Lab activity): Correct Solution (1dad-w1g6-9ik5-7f98-s)
• While loops and for loops: Correct Solution (1pyp-0gwo-1e1k-149)
• Closures and event handling: Correct Solution (Lwjo-equo-dage-pgcg)
• Class relationships: Correct Solution (rk7L-28gk-ztu0-gojL)
• Class declarations and object modeling: Correct Solution (17vy-usvi-w5L4-1a7f-p)
• Booleans and conditionals: Correct Solution (5n8h-455j-c6et-w3ru)