One Enum per File?

[Joan]

Since an Enum is a class, is it expected that
you put only one Enum in a file? This could
make for a whole lot of files for some applications.

 

[Roedy Green]

Since an Enum is a class, is it expected that
you put only one Enum in a file? This could
make for a whole lot of files for some applications.

One file per enum usually works out best. If the enum is not public,
you can make it a top level non-nested class with package visibility

--
Bush crime family lost/embezzled $3 trillion from Pentagon.
Complicit Bush-friendly media keeps mum. Rumsfeld confesses on video.
http://www.infowars.com/articles/us/mckinney_grills_rumsfeld.htm

Canadian Mind Products, Roedy Green.
See http://mindprod.com/iraq.html photos of Bush's war crimes

 

[Jim McMaster]

Since an Enum is a class, is it expected that
you put only one Enum in a file? This could
make for a whole lot of files for some applications.

The enum defines the structure of the enum type, and also the
definitions of all the member types of the enum. You can have:

public enum MyEnum {
MyType1, MyType2, MyType3
}

to define an enum with three types.

 

[Dale King]

One file per enum usually works out best. If the enum is not public,
you can make it a top level non-nested class with package visibility

I would say that it would probably be rare that you want a top-level
enum. Usually the enum is going to be associated with some API and
defined in that class or intreface.

I've actually defined an enum nested within another enum.