Enums taking in enums?

[rizowski]

Is there a way to make an enum have an enum as one of its constructors parameters?

package piece;

import game.operation.Board;
import game.operation.Location;

public enum Type {
	

	CHEESE(color){

               //methods go here

	};

	public static Color color;

	private Type( Color color) {
		this.[COLOR="red"]color[/COLOR] = Color.valueOf(Color.class, color.toString());
	}
}

I have tried to use the static method .valueOf(); which works. But the problem is that I get an error when setting it to static. It says

"Cannot refer to the static enum field Type.color within an initializer"

Color is it's own enum. I want to define that my cheese is color Blue, black, green or what ever I have put in Color enum.

[Fubarable]

For one, don't make Color static if each enum member is to have its own color. And don't use valueOf. Just accept the color passed in:

public enum Type {
	

	CHEESE(Color.FOO){ // show which Color here

               //methods go here

	};

	private Color color;

	private Type( Color color) {
		this.color = color;
	}

	public  getColor( ) {
		return color;
	}
}

[rizowski]

Is .FOO whatever color constant/enum I have in Color? like Color.WHITE?

[Fubarable]

Is .FOO whatever color constant/enum I have in Color? like Color.WHITE?

Yes. If that doesn't work for you, then please elaborate more on the nature of your problem.

[rizowski]

What I am trying to make it abstract so that it doesn't need to be a specific color. it "can" be blue or yellow.

[Fubarable]

What I am trying to make it abstract so that it doesn't need to be a specific color. it "can" be blue or yellow.

Sorry but I don't understand what you mean here. If you want to change the state of a Java object, you usually do so by setter methods. Abstract has nothing to do with this, nor can you have abstract enums. I think that if you still need help, you'll have to give us more detail. Assume that we can't read your mind or guess what your un-shown code looks like.

[rizowski]

It is probably not really Abstraction I believe the word i was actually looking for is polymorphism. I don't really want to set the specific color of cheese. Because it could be black, blue, or green. I am really unsure how I would be able to make it generic so that if I called the enum "Type" I could say something like Type.Cheese.color.toString(); and it would print out the color of the cheese. The way I have my Color enum is Like so:

public enum Color {

	WHITE("White", "L"),
	BLACK("Black", "D");
	
	public final String COLOR;
	public final String SHORT_COLOR;
	private Color(String color, String shortColor) {
		this.COLOR = color;
		this.SHORT_COLOR = shortColor;
	}
}

I don't want to necessarily hard code the color mainly because it could either be black, blue, or green.

I hope this sheds some light on my position :D

[dlorde]

You seem to be confused about what the enum value CHEESE is in your Type enum. CHEESE is a specific, once-only instantiation of Type that must be given an explicit Color. The Type constructor is what is called by, for example, the CHEESE(Color.blue) statement in the Type body. Enum values are instantiated once (with specific parameters if required), they aren't dynamic.

If you want cheeses of different kinds by color, you should define a Cheese enum with the different colors:

public enum Cheese {
    CHEDDAR(Color.white) {
       
    },
    STILTON(Color.blue){
           //methods go here
    };
    ...  // etc.
    
    public Color color;

    private Cheese(Color color) {
	this.color = color;
    }
}

If you really want to be able to instantiate a cheese object with a variable Color parameter, you need to write a Cheese class, not an enum.