Does using an enum make an application less portable?

Question

I know this question sounds bizarre, but that's what my manager told me. When I proposed a new design that made use of an enum, he said, "No, ...", and then went on to make an offhand comment that making use of such a construct actually makes the application "less portable".

Is this true? I suspect that it's not.

Answer 1

You should ask him for me details... it does mean you wouldn't be able to compile the code in Java 1.4 or earlier, but that's not a terribly good justification.

Sounds like your manager may be confused... but you should always press for details.