Re: Nested enums

I recognise that name..

Try not to design in terms of enums, but in terms of interfaces. If
the implementation ends up looking like an enum, then sure, for
clarity, make it an enum.

In this example, I would have something like:

interface MajorCommand
{
        Iterable<SubCommand> possibleValues();
}

interface SubCommand
{
}

enum Commands
{
        LOGON
        {
                public Iterable<SubCommand> possibleValues()
                {
                        return Collections.emptySet();
                }
        },
        QUIT
        {
                public Iterable<SubCommand> possibleValues()
                {
                        SubCommand[]
subCommands=QuitSubCommands.values();
                        return Arrays.asList(subCommands);
                }
        },
        LIGHT
        {
                public Iterable<SubCommand> possibleValues()
                {
                        SubCommand[]
subCommands=LightSubCommands.values();
                        return Arrays.asList(subCommands);
                }
        }
}

enum QuitSubCommands
{
        IMMEDIATELY,
        DELAY
}

enum LightSubCommands
{
        TURN_ON,
        TURN_OFF
}

unomystEz wrote: