Comments on: Getting rid of switch statements with Java Enums

By: Jonathan Marler

Jonathan Marler — Thu, 15 Apr 2010 21:04:17 +0000

Very useful, a great natural design for using enums.

Also, this is not a big deal, but in order to compile your example I had to add a semi-colon at the end of line 7.

1.enum Friend {
2. Joey {
3. Friend bestFriend() { return Chandler; }
4. },
5. Chandler {
6. Friend bestFriend() { return Joey; }
7. }
8. abstract Friend bestFriend();
9.}

By: Bill Bartmann

Bill Bartmann — Thu, 03 Sep 2009 16:36:35 +0000

Cool site, love the info.

By: Kris Kemper

Kris Kemper — Thu, 23 Jul 2009 02:05:42 +0000

Thanks Vivek! I generated the code using Jad - decompiler for eclipse. It became hard to find for a while since the main website went down, but there are mirrors for it now. Check out: http://www.varaneckas.com/jad

By: vivek

vivek — Tue, 21 Jul 2009 06:22:38 +0000

good article. I don’t know how you got the generated code for Enum but it is useful to see how Enum are treated internally. Makes it very clear that each enum is a full fledged object instance.

By: Dmitry Kandalov

Dmitry Kandalov — Mon, 20 Oct 2008 12:31:18 +0000

Great post. I’ve had a similar problem with enums but I didn’t dig so deep why forward referencing doesn’t work.

enum Friend {
Joey(Friend.Chandler),
Chandler(Joey);
…
}
won’t compile with Sun compiler (jdk1.6_06). So using anonymous enums is probably the only way to go.