Understanding Enums in Java

What are java enums? How do they work? Where could I used them and how?

Can I do without using enums in an app or are they so powerful that Its better to use them than ignore them?

edited Sep 19 '09 at 18:55

cletus

505k139839909

asked Sep 14 '09 at 5:35

Kevin Boyd

6,2932372123

add a comment |

What are java enums? How do they work? Where could I used them and how?

Can I do without using enums in an app or are they so powerful that Its better to use them than ignore them?

edited Sep 19 '09 at 18:55

cletus

505k139839909

asked Sep 14 '09 at 5:35

Kevin Boyd

6,2932372123

add a comment |

What are java enums? How do they work? Where could I used them and how?

Can I do without using enums in an app or are they so powerful that Its better to use them than ignore them?

edited Sep 19 '09 at 18:55

cletus

505k139839909

asked Sep 14 '09 at 5:35

Kevin Boyd

6,2932372123

What are java enums? How do they work? Where could I used them and how?

Can I do without using enums in an app or are they so powerful that Its better to use them than ignore them?

java enums

edited Sep 19 '09 at 18:55

cletus

505k139839909

asked Sep 14 '09 at 5:35

Kevin Boyd

6,2932372123

edited Sep 19 '09 at 18:55

cletus

505k139839909

asked Sep 14 '09 at 5:35

Kevin Boyd

6,2932372123

edited Sep 19 '09 at 18:55

cletus

505k139839909

edited Sep 19 '09 at 18:55

cletus

505k139839909

edited Sep 19 '09 at 18:55

cletus

505k139839909

asked Sep 14 '09 at 5:35

Kevin Boyd

6,2932372123

asked Sep 14 '09 at 5:35

Kevin Boyd

6,2932372123

asked Sep 14 '09 at 5:35

Kevin Boyd

6,2932372123

add a comment |

6 Answers
6

active

oldest

votes

Enums in Java 5+ are basically classes that have a predefined set of instances. They are intended as a replacement for, say, a collection of integer constants. They are preferably to constants as they can enforce type safety.

So instead of:

public class Suit {

  public final static int SPADES = 1;

  public final static int CLUBS = 2

  public final static int HEARTS = 3;

  public final static int DIAMONDS = 4;

}

you have:

public enum Suit {

  SPADES, CLUBS, HEARTS, DIAMONDS

}

The advantages are:

Type safety. You can declare a function argument, return type, class member or local variable to be a particular Enum type and the compiler will enforce type safety;

Enums are basically classes. They can implement interfaces, have behaviour and so on.

The type safety is an issue because in the first example, these are valid statements:

int i = Suit.DIAMONDS * Suit.CLUBS;

or you can pass in 11 to a function expecting a suit. You can't do that with a typesafe enum.

You can use a class for Suit to provide type safety and this was the solution before Java 5. Josh Bloch (in Effective Java, which is a must read for Java programmers imho) promoted the typesafe enum pattern that became the Java 5+ enum. It has a fair amount of boilerplate on it and some corner cases that people didn't tend to cater for, such as serialization not calling a constructor and to ensure you only got one instance you had to override the readResolve() method.

For example:

public enum CardColour {

  RED, BLACK

}



public enum Suit {

  SPADES(CardColour.BLACK),

  CLUBS(CardColour.BLACK),

  HEARTS(CardColour.RED),

  DIAMONDS(CardColour.RED);



  private final CardColour colour;



  Suit(CardColour colour) { this.colour = colour; }



  public CardColour getColour() { return colour; }

}

Edit: Sun has an introduction to typesafe enums.

As for interfaces, they really complement enums rather than being an alternative. Like you could say that Suit is an interface and you'd have this:

public interface Suit {

  CardColour getColour();

}

The problem is that you could go and define 300 different suits and you could also define Spades several times. Another advantage of enums is (classloading corner cases notwithstanding) is that there is only one instance of each enum value. Typically this is referred to as having a canonical value, meaning this equality holds true:

a.equals(b) == b.equals(a) == (a == b)

for all a, b that are instances of a particular Enum. This means that instead of writing:

if (card.getSuit().equals(Suit.SPADES)) { ... }

you can write:

if (card.getSuit() == Suit.SPADES) { ... }

which is quicker and typically easier to read. Plus IDEs will typically give you feedback if you're comparing enums of different types saying they can't possibly be equal, which can be a useful and early form of error-checking.

edited Feb 25 '13 at 3:52

Daryl Spitzer

51.6k58142162

answered Sep 14 '09 at 5:41

cletus

505k139839909

1

Sun's Guide (java.sun.com/j2se/1.5.0/docs/guide/language/enums.html) offers a good sight of their potential; I'd suggest adding a reference for further reading.

– Bryan Menard
Sep 14 '09 at 5:50

@cletus... couldn't an Interface be used for the same?

– Kevin Boyd
Sep 14 '09 at 5:51

@cletus: I did not understand the "type safety" part of it. Doesn't a Java class provide type safety?

– Kevin Boyd
Sep 14 '09 at 5:56

1

@Kevin: As opposed to C#, for instance, it is not possible to use explicit cast to "fake" an Enum (MyEnum e = (MyEnum)45;)

– Bryan Menard
Sep 14 '09 at 6:00

1

@Kevin: @cletus is comparing enums (typesafe) versus "mock enums using ints" (not typesafe). Read the answer again.

– Stephen C
Sep 14 '09 at 10:56

add a comment |

Think of Enum as follows

public class MyEnum {



    // Object instantiated at declaration

    public static final MyEnum ONE = new MyEnum();

    public static final MyEnum TWO = new MyEnum();

    public static final MyEnum THREE = new MyEnum();



    // Notice a private constructor 

    // There is no way outside MyEnum class call it

    private MyEnum() { ... }





}

So a MyEnum as a enum would be

public enum MyEnum {

    ONE,

    TWO,

    THREE;

}

Both are similar

regards,

edited Sep 14 '09 at 5:47

answered Sep 14 '09 at 5:42

Arthur Ronald

27k1696132

Note, all enums in java extends java.lang.Enum by default. So that, no enum shall extends any other but shall implements any number of interfaces. This is because java doesn't allow multiple inheritance.

– Damith
Sep 13 '18 at 2:24

add a comment |

Sun's enum documentation is probably the best explanation. Of course you can do without them as Java programmers certainly did until Java 1.5 was released. You would typically accomplish the same thing by using constants in versions of Java before 1.5. But enums are a nice convenience.

answered Sep 14 '09 at 5:39

Asaph

125k19161177

Why was it included in Java 1.5? Is it that powerful?

– Kevin Boyd
Sep 14 '09 at 5:48

add a comment |

If the situation doesn't come up then you don't need them.

They allow you to have a well defined set of things, for instance if you wanted to represent the states of matter you could have:

enum MatterState {

    Solid,

    Liquid,

    Gas;

}

Where they beat the old style of using objects to represent sets in a number of ways, some of which are:

You can use them in switch
statements.

Less code.

Built in
to/from string.

answered Sep 14 '09 at 5:41

Tom

33k43153

add a comment |

To add some additional information to find out it more, it is better to start with concept of a variable and its values. As I am sure you now, each variable has a declared type (such as Java primitive types). Each type has its own corresponding values. For example a variables with the char type can accept all individual characters as its values. So it is very helpful when you want to declare a variable can accept all set of character constants. For instance all character constants are acceptable and meaningful for aCharToStopProgram variable:

char aCharToStopProgram = getUserInput();

However, what about when you have a limited value, I mean value's domain of your variable is restricted to special values. For example you have userChoice which keeps value of system multiple choice question. So just 'a', 'b', 'c', 'd' is meaningful. You don't want in another section of your program code(or any other reason) this variable is assigned with meaningless values such as 's'. Now is it true to use a char primitive type for our variable which can accept any character constant, such following.

char userChoice = getUserChoice();

In this situations Java provides Enumerated Types. It means via enum keyword you can define a new class that has limited and fixed instances which is call named values(you can not creat new objects). For example:

enum MultipleChoiceAnswer { A, B, C, D };

public enum MultipleChoiceAnswer {



    A('a'), B('b'), C('c'), D('d');



    private char choice;



    private MultipleChoiceAnswer(char choice) { 

        this.choice = choice; 

    }



    public String getChoice() { 

        return choice; 

    }

}

As result you can define a variable with your own type:

MultipleChoiceAnswer userChoice = getUserChoice();//OR MultipleChoiceAnswer.A

answered Dec 4 '17 at 17:49

MMKarami

30426

add a comment |

From my interpretation, enums are more for readability than anything else. They are basically used to replace values like 1-6 with more descriptive names, like [Happy, Sad, Angry, etc]
You should use them whenever you need to use a small set of variables to describe the solution that you are expecting.

answered Sep 14 '09 at 5:42

bogertron

1,75811726

2

@bogerton: actually, there are significant typesafety advantages to using Java enums; see @cletus's excellent answer.

– Stephen C
Sep 14 '09 at 10:58

add a comment |

Your Answer

StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});

}
});

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f1419835%2funderstanding-enums-in-java%23new-answer', 'question_page');
}
);

Post as a guest

Name

Required, but never shown

6 Answers
6

active

oldest

votes

6 Answers
6

active

oldest

votes

So instead of:

public class Suit {

  public final static int SPADES = 1;

  public final static int CLUBS = 2

  public final static int HEARTS = 3;

  public final static int DIAMONDS = 4;

}

you have:

public enum Suit {

  SPADES, CLUBS, HEARTS, DIAMONDS

}

The advantages are:

Type safety. You can declare a function argument, return type, class member or local variable to be a particular Enum type and the compiler will enforce type safety;

Enums are basically classes. They can implement interfaces, have behaviour and so on.

The type safety is an issue because in the first example, these are valid statements:

int i = Suit.DIAMONDS * Suit.CLUBS;

or you can pass in 11 to a function expecting a suit. You can't do that with a typesafe enum.

For example:

public enum CardColour {

  RED, BLACK

}



public enum Suit {

  SPADES(CardColour.BLACK),

  CLUBS(CardColour.BLACK),

  HEARTS(CardColour.RED),

  DIAMONDS(CardColour.RED);



  private final CardColour colour;



  Suit(CardColour colour) { this.colour = colour; }



  public CardColour getColour() { return colour; }

}

Edit: Sun has an introduction to typesafe enums.

As for interfaces, they really complement enums rather than being an alternative. Like you could say that Suit is an interface and you'd have this:

public interface Suit {

  CardColour getColour();

}

a.equals(b) == b.equals(a) == (a == b)

for all a, b that are instances of a particular Enum. This means that instead of writing:

if (card.getSuit().equals(Suit.SPADES)) { ... }

you can write:

if (card.getSuit() == Suit.SPADES) { ... }

edited Feb 25 '13 at 3:52

Daryl Spitzer

51.6k58142162

answered Sep 14 '09 at 5:41

cletus

505k139839909

1

Sun's Guide (java.sun.com/j2se/1.5.0/docs/guide/language/enums.html) offers a good sight of their potential; I'd suggest adding a reference for further reading.

– Bryan Menard
Sep 14 '09 at 5:50

@cletus... couldn't an Interface be used for the same?

– Kevin Boyd
Sep 14 '09 at 5:51

@cletus: I did not understand the "type safety" part of it. Doesn't a Java class provide type safety?

– Kevin Boyd
Sep 14 '09 at 5:56

1

@Kevin: As opposed to C#, for instance, it is not possible to use explicit cast to "fake" an Enum (MyEnum e = (MyEnum)45;)

– Bryan Menard
Sep 14 '09 at 6:00

1

@Kevin: @cletus is comparing enums (typesafe) versus "mock enums using ints" (not typesafe). Read the answer again.

– Stephen C
Sep 14 '09 at 10:56

add a comment |

So instead of:

public class Suit {

  public final static int SPADES = 1;

  public final static int CLUBS = 2

  public final static int HEARTS = 3;

  public final static int DIAMONDS = 4;

}

you have:

public enum Suit {

  SPADES, CLUBS, HEARTS, DIAMONDS

}

The advantages are:

Type safety. You can declare a function argument, return type, class member or local variable to be a particular Enum type and the compiler will enforce type safety;

Enums are basically classes. They can implement interfaces, have behaviour and so on.

The type safety is an issue because in the first example, these are valid statements:

int i = Suit.DIAMONDS * Suit.CLUBS;

or you can pass in 11 to a function expecting a suit. You can't do that with a typesafe enum.

For example:

public enum CardColour {

  RED, BLACK

}



public enum Suit {

  SPADES(CardColour.BLACK),

  CLUBS(CardColour.BLACK),

  HEARTS(CardColour.RED),

  DIAMONDS(CardColour.RED);



  private final CardColour colour;



  Suit(CardColour colour) { this.colour = colour; }



  public CardColour getColour() { return colour; }

}

Edit: Sun has an introduction to typesafe enums.

As for interfaces, they really complement enums rather than being an alternative. Like you could say that Suit is an interface and you'd have this:

public interface Suit {

  CardColour getColour();

}

a.equals(b) == b.equals(a) == (a == b)

for all a, b that are instances of a particular Enum. This means that instead of writing:

if (card.getSuit().equals(Suit.SPADES)) { ... }

you can write:

if (card.getSuit() == Suit.SPADES) { ... }

edited Feb 25 '13 at 3:52

Daryl Spitzer

51.6k58142162

answered Sep 14 '09 at 5:41

cletus

505k139839909

1

Sun's Guide (java.sun.com/j2se/1.5.0/docs/guide/language/enums.html) offers a good sight of their potential; I'd suggest adding a reference for further reading.

– Bryan Menard
Sep 14 '09 at 5:50

@cletus... couldn't an Interface be used for the same?

– Kevin Boyd
Sep 14 '09 at 5:51

@cletus: I did not understand the "type safety" part of it. Doesn't a Java class provide type safety?

– Kevin Boyd
Sep 14 '09 at 5:56

1

@Kevin: As opposed to C#, for instance, it is not possible to use explicit cast to "fake" an Enum (MyEnum e = (MyEnum)45;)

– Bryan Menard
Sep 14 '09 at 6:00

1

@Kevin: @cletus is comparing enums (typesafe) versus "mock enums using ints" (not typesafe). Read the answer again.

– Stephen C
Sep 14 '09 at 10:56

add a comment |

So instead of:

public class Suit {

  public final static int SPADES = 1;

  public final static int CLUBS = 2

  public final static int HEARTS = 3;

  public final static int DIAMONDS = 4;

}

you have:

public enum Suit {

  SPADES, CLUBS, HEARTS, DIAMONDS

}

The advantages are:

Type safety. You can declare a function argument, return type, class member or local variable to be a particular Enum type and the compiler will enforce type safety;

Enums are basically classes. They can implement interfaces, have behaviour and so on.

The type safety is an issue because in the first example, these are valid statements:

int i = Suit.DIAMONDS * Suit.CLUBS;

or you can pass in 11 to a function expecting a suit. You can't do that with a typesafe enum.

For example:

public enum CardColour {

  RED, BLACK

}



public enum Suit {

  SPADES(CardColour.BLACK),

  CLUBS(CardColour.BLACK),

  HEARTS(CardColour.RED),

  DIAMONDS(CardColour.RED);



  private final CardColour colour;



  Suit(CardColour colour) { this.colour = colour; }



  public CardColour getColour() { return colour; }

}

Edit: Sun has an introduction to typesafe enums.

As for interfaces, they really complement enums rather than being an alternative. Like you could say that Suit is an interface and you'd have this:

public interface Suit {

  CardColour getColour();

}

a.equals(b) == b.equals(a) == (a == b)

for all a, b that are instances of a particular Enum. This means that instead of writing:

if (card.getSuit().equals(Suit.SPADES)) { ... }

you can write:

if (card.getSuit() == Suit.SPADES) { ... }

edited Feb 25 '13 at 3:52

Daryl Spitzer

51.6k58142162

answered Sep 14 '09 at 5:41

cletus

505k139839909

So instead of:

public class Suit {

  public final static int SPADES = 1;

  public final static int CLUBS = 2

  public final static int HEARTS = 3;

  public final static int DIAMONDS = 4;

}

you have:

public enum Suit {

  SPADES, CLUBS, HEARTS, DIAMONDS

}

The advantages are:

Type safety. You can declare a function argument, return type, class member or local variable to be a particular Enum type and the compiler will enforce type safety;

Enums are basically classes. They can implement interfaces, have behaviour and so on.

The type safety is an issue because in the first example, these are valid statements:

int i = Suit.DIAMONDS * Suit.CLUBS;

or you can pass in 11 to a function expecting a suit. You can't do that with a typesafe enum.

For example:

public enum CardColour {

  RED, BLACK

}



public enum Suit {

  SPADES(CardColour.BLACK),

  CLUBS(CardColour.BLACK),

  HEARTS(CardColour.RED),

  DIAMONDS(CardColour.RED);



  private final CardColour colour;



  Suit(CardColour colour) { this.colour = colour; }



  public CardColour getColour() { return colour; }

}

Edit: Sun has an introduction to typesafe enums.

As for interfaces, they really complement enums rather than being an alternative. Like you could say that Suit is an interface and you'd have this:

public interface Suit {

  CardColour getColour();

}

a.equals(b) == b.equals(a) == (a == b)

for all a, b that are instances of a particular Enum. This means that instead of writing:

if (card.getSuit().equals(Suit.SPADES)) { ... }

you can write:

if (card.getSuit() == Suit.SPADES) { ... }

edited Feb 25 '13 at 3:52

Daryl Spitzer

51.6k58142162

answered Sep 14 '09 at 5:41

cletus

505k139839909

edited Feb 25 '13 at 3:52

Daryl Spitzer

51.6k58142162

edited Feb 25 '13 at 3:52

Daryl Spitzer

51.6k58142162

edited Feb 25 '13 at 3:52

Daryl Spitzer

51.6k58142162

answered Sep 14 '09 at 5:41

cletus

505k139839909

answered Sep 14 '09 at 5:41

cletus

505k139839909

answered Sep 14 '09 at 5:41

cletus

505k139839909

1

Sun's Guide (java.sun.com/j2se/1.5.0/docs/guide/language/enums.html) offers a good sight of their potential; I'd suggest adding a reference for further reading.

– Bryan Menard
Sep 14 '09 at 5:50

@cletus... couldn't an Interface be used for the same?

– Kevin Boyd
Sep 14 '09 at 5:51

@cletus: I did not understand the "type safety" part of it. Doesn't a Java class provide type safety?

– Kevin Boyd
Sep 14 '09 at 5:56

1

@Kevin: As opposed to C#, for instance, it is not possible to use explicit cast to "fake" an Enum (MyEnum e = (MyEnum)45;)

– Bryan Menard
Sep 14 '09 at 6:00

1

@Kevin: @cletus is comparing enums (typesafe) versus "mock enums using ints" (not typesafe). Read the answer again.

– Stephen C
Sep 14 '09 at 10:56

add a comment |

1

Sun's Guide (java.sun.com/j2se/1.5.0/docs/guide/language/enums.html) offers a good sight of their potential; I'd suggest adding a reference for further reading.

– Bryan Menard
Sep 14 '09 at 5:50

@cletus... couldn't an Interface be used for the same?

– Kevin Boyd
Sep 14 '09 at 5:51

@cletus: I did not understand the "type safety" part of it. Doesn't a Java class provide type safety?

– Kevin Boyd
Sep 14 '09 at 5:56

1

@Kevin: As opposed to C#, for instance, it is not possible to use explicit cast to "fake" an Enum (MyEnum e = (MyEnum)45;)

– Bryan Menard
Sep 14 '09 at 6:00

1

@Kevin: @cletus is comparing enums (typesafe) versus "mock enums using ints" (not typesafe). Read the answer again.

– Stephen C
Sep 14 '09 at 10:56

Sun's Guide (java.sun.com/j2se/1.5.0/docs/guide/language/enums.html) offers a good sight of their potential; I'd suggest adding a reference for further reading.

– Bryan Menard
Sep 14 '09 at 5:50

@cletus... couldn't an Interface be used for the same?

– Kevin Boyd
Sep 14 '09 at 5:51

@cletus: I did not understand the "type safety" part of it. Doesn't a Java class provide type safety?

– Kevin Boyd
Sep 14 '09 at 5:56

@Kevin: As opposed to C#, for instance, it is not possible to use explicit cast to "fake" an Enum (MyEnum e = (MyEnum)45;)

– Bryan Menard
Sep 14 '09 at 6:00

@Kevin: @cletus is comparing enums (typesafe) versus "mock enums using ints" (not typesafe). Read the answer again.

– Stephen C
Sep 14 '09 at 10:56

add a comment |

Think of Enum as follows

public class MyEnum {



    // Object instantiated at declaration

    public static final MyEnum ONE = new MyEnum();

    public static final MyEnum TWO = new MyEnum();

    public static final MyEnum THREE = new MyEnum();



    // Notice a private constructor 

    // There is no way outside MyEnum class call it

    private MyEnum() { ... }





}

So a MyEnum as a enum would be

public enum MyEnum {

    ONE,

    TWO,

    THREE;

}

Both are similar

regards,

edited Sep 14 '09 at 5:47

answered Sep 14 '09 at 5:42

Arthur Ronald

27k1696132

Note, all enums in java extends java.lang.Enum by default. So that, no enum shall extends any other but shall implements any number of interfaces. This is because java doesn't allow multiple inheritance.

– Damith
Sep 13 '18 at 2:24

add a comment |

Think of Enum as follows

public class MyEnum {



    // Object instantiated at declaration

    public static final MyEnum ONE = new MyEnum();

    public static final MyEnum TWO = new MyEnum();

    public static final MyEnum THREE = new MyEnum();



    // Notice a private constructor 

    // There is no way outside MyEnum class call it

    private MyEnum() { ... }





}

So a MyEnum as a enum would be

public enum MyEnum {

    ONE,

    TWO,

    THREE;

}

Both are similar

regards,

edited Sep 14 '09 at 5:47

answered Sep 14 '09 at 5:42

Arthur Ronald

27k1696132

Note, all enums in java extends java.lang.Enum by default. So that, no enum shall extends any other but shall implements any number of interfaces. This is because java doesn't allow multiple inheritance.

– Damith
Sep 13 '18 at 2:24

add a comment |

Think of Enum as follows

public class MyEnum {



    // Object instantiated at declaration

    public static final MyEnum ONE = new MyEnum();

    public static final MyEnum TWO = new MyEnum();

    public static final MyEnum THREE = new MyEnum();



    // Notice a private constructor 

    // There is no way outside MyEnum class call it

    private MyEnum() { ... }





}

So a MyEnum as a enum would be

public enum MyEnum {

    ONE,

    TWO,

    THREE;

}

Both are similar

regards,

edited Sep 14 '09 at 5:47

answered Sep 14 '09 at 5:42

Arthur Ronald

27k1696132

Think of Enum as follows

public class MyEnum {



    // Object instantiated at declaration

    public static final MyEnum ONE = new MyEnum();

    public static final MyEnum TWO = new MyEnum();

    public static final MyEnum THREE = new MyEnum();



    // Notice a private constructor 

    // There is no way outside MyEnum class call it

    private MyEnum() { ... }





}

So a MyEnum as a enum would be

public enum MyEnum {

    ONE,

    TWO,

    THREE;

}

Both are similar

regards,

edited Sep 14 '09 at 5:47

answered Sep 14 '09 at 5:42

Arthur Ronald

27k1696132

edited Sep 14 '09 at 5:47

answered Sep 14 '09 at 5:42

Arthur Ronald

27k1696132

answered Sep 14 '09 at 5:42

Arthur Ronald

27k1696132

answered Sep 14 '09 at 5:42

Arthur Ronald

27k1696132

Note, all enums in java extends java.lang.Enum by default. So that, no enum shall extends any other but shall implements any number of interfaces. This is because java doesn't allow multiple inheritance.

– Damith
Sep 13 '18 at 2:24

add a comment |

Note, all enums in java extends java.lang.Enum by default. So that, no enum shall extends any other but shall implements any number of interfaces. This is because java doesn't allow multiple inheritance.

– Damith
Sep 13 '18 at 2:24

Note, all enums in java extends java.lang.Enum by default. So that, no enum shall extends any other but shall implements any number of interfaces. This is because java doesn't allow multiple inheritance.

– Damith
Sep 13 '18 at 2:24

add a comment |

answered Sep 14 '09 at 5:39

Asaph

125k19161177

Why was it included in Java 1.5? Is it that powerful?

– Kevin Boyd
Sep 14 '09 at 5:48

add a comment |

answered Sep 14 '09 at 5:39

Asaph

125k19161177

Why was it included in Java 1.5? Is it that powerful?

– Kevin Boyd
Sep 14 '09 at 5:48

add a comment |

answered Sep 14 '09 at 5:39

Asaph

125k19161177

answered Sep 14 '09 at 5:39

Asaph

125k19161177

answered Sep 14 '09 at 5:39

Asaph

125k19161177

answered Sep 14 '09 at 5:39

Asaph

125k19161177

answered Sep 14 '09 at 5:39

Asaph

125k19161177

Why was it included in Java 1.5? Is it that powerful?

– Kevin Boyd
Sep 14 '09 at 5:48

add a comment |

Why was it included in Java 1.5? Is it that powerful?

– Kevin Boyd
Sep 14 '09 at 5:48

Why was it included in Java 1.5? Is it that powerful?

– Kevin Boyd
Sep 14 '09 at 5:48

add a comment |

If the situation doesn't come up then you don't need them.

They allow you to have a well defined set of things, for instance if you wanted to represent the states of matter you could have:

enum MatterState {

    Solid,

    Liquid,

    Gas;

}

Where they beat the old style of using objects to represent sets in a number of ways, some of which are:

You can use them in switch
statements.

Less code.

Built in
to/from string.

answered Sep 14 '09 at 5:41

Tom

33k43153

add a comment |

If the situation doesn't come up then you don't need them.

They allow you to have a well defined set of things, for instance if you wanted to represent the states of matter you could have:

enum MatterState {

    Solid,

    Liquid,

    Gas;

}

Where they beat the old style of using objects to represent sets in a number of ways, some of which are:

You can use them in switch
statements.

Less code.

Built in
to/from string.

answered Sep 14 '09 at 5:41

Tom

33k43153

add a comment |

If the situation doesn't come up then you don't need them.

They allow you to have a well defined set of things, for instance if you wanted to represent the states of matter you could have:

enum MatterState {

    Solid,

    Liquid,

    Gas;

}

Where they beat the old style of using objects to represent sets in a number of ways, some of which are:

You can use them in switch
statements.

Less code.

Built in
to/from string.

answered Sep 14 '09 at 5:41

Tom

33k43153

If the situation doesn't come up then you don't need them.

They allow you to have a well defined set of things, for instance if you wanted to represent the states of matter you could have:

enum MatterState {

    Solid,

    Liquid,

    Gas;

}

Where they beat the old style of using objects to represent sets in a number of ways, some of which are:

You can use them in switch
statements.

Less code.

Built in
to/from string.

answered Sep 14 '09 at 5:41

Tom

33k43153

answered Sep 14 '09 at 5:41

Tom

33k43153

answered Sep 14 '09 at 5:41

Tom

33k43153

answered Sep 14 '09 at 5:41

Tom

33k43153

add a comment |

char aCharToStopProgram = getUserInput();

char userChoice = getUserChoice();

enum MultipleChoiceAnswer { A, B, C, D };

public enum MultipleChoiceAnswer {



    A('a'), B('b'), C('c'), D('d');



    private char choice;



    private MultipleChoiceAnswer(char choice) { 

        this.choice = choice; 

    }



    public String getChoice() { 

        return choice; 

    }

}

As result you can define a variable with your own type:

MultipleChoiceAnswer userChoice = getUserChoice();//OR MultipleChoiceAnswer.A

answered Dec 4 '17 at 17:49

MMKarami

30426

add a comment |

char aCharToStopProgram = getUserInput();

char userChoice = getUserChoice();

enum MultipleChoiceAnswer { A, B, C, D };

public enum MultipleChoiceAnswer {



    A('a'), B('b'), C('c'), D('d');



    private char choice;



    private MultipleChoiceAnswer(char choice) { 

        this.choice = choice; 

    }



    public String getChoice() { 

        return choice; 

    }

}

As result you can define a variable with your own type:

MultipleChoiceAnswer userChoice = getUserChoice();//OR MultipleChoiceAnswer.A

answered Dec 4 '17 at 17:49

MMKarami

30426

add a comment |

char aCharToStopProgram = getUserInput();

char userChoice = getUserChoice();

enum MultipleChoiceAnswer { A, B, C, D };

public enum MultipleChoiceAnswer {



    A('a'), B('b'), C('c'), D('d');



    private char choice;



    private MultipleChoiceAnswer(char choice) { 

        this.choice = choice; 

    }



    public String getChoice() { 

        return choice; 

    }

}

As result you can define a variable with your own type:

MultipleChoiceAnswer userChoice = getUserChoice();//OR MultipleChoiceAnswer.A

answered Dec 4 '17 at 17:49

MMKarami

30426

char aCharToStopProgram = getUserInput();

char userChoice = getUserChoice();

enum MultipleChoiceAnswer { A, B, C, D };

public enum MultipleChoiceAnswer {



    A('a'), B('b'), C('c'), D('d');



    private char choice;



    private MultipleChoiceAnswer(char choice) { 

        this.choice = choice; 

    }



    public String getChoice() { 

        return choice; 

    }

}

As result you can define a variable with your own type:

MultipleChoiceAnswer userChoice = getUserChoice();//OR MultipleChoiceAnswer.A

answered Dec 4 '17 at 17:49

MMKarami

30426

answered Dec 4 '17 at 17:49

MMKarami

30426

answered Dec 4 '17 at 17:49

MMKarami

30426

answered Dec 4 '17 at 17:49

MMKarami

30426

add a comment |

answered Sep 14 '09 at 5:42

bogertron

1,75811726

2

@bogerton: actually, there are significant typesafety advantages to using Java enums; see @cletus's excellent answer.

– Stephen C
Sep 14 '09 at 10:58

add a comment |

answered Sep 14 '09 at 5:42

bogertron

1,75811726

2

@bogerton: actually, there are significant typesafety advantages to using Java enums; see @cletus's excellent answer.

– Stephen C
Sep 14 '09 at 10:58

add a comment |

answered Sep 14 '09 at 5:42

bogertron

1,75811726

answered Sep 14 '09 at 5:42

bogertron

1,75811726

answered Sep 14 '09 at 5:42

bogertron

1,75811726

answered Sep 14 '09 at 5:42

bogertron

1,75811726

answered Sep 14 '09 at 5:42

bogertron

1,75811726

2

@bogerton: actually, there are significant typesafety advantages to using Java enums; see @cletus's excellent answer.

– Stephen C
Sep 14 '09 at 10:58

add a comment |

2

@bogerton: actually, there are significant typesafety advantages to using Java enums; see @cletus's excellent answer.

– Stephen C
Sep 14 '09 at 10:58

@bogerton: actually, there are significant typesafety advantages to using Java enums; see @cletus's excellent answer.

– Stephen C
Sep 14 '09 at 10:58

add a comment |

draft saved

draft discarded

Thanks for contributing an answer to Stack Overflow!

Please be sure to answer the question. Provide details and share your research!

But avoid …

Asking for help, clarification, or responding to other answers.

Making statements based on opinion; back them up with references or personal experience.

To learn more, see our tips on writing great answers.

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Name

Required, but never shown

Name

Required, but never shown

This page is only for reference, If you need detailed information, please check here

Search This Blog

Ufyukyu