6

I've recently started working the C++/CLI managed code, but I've always defined enums like so:

enum FV_MODE
{
    IDLE,DRAG,ADD_HITBOX,ADD_HURTBOX
};

Until today, when I was hit with the error message:

cannot define an unmanaged enum 'FViewer::FV_MODE' inside managed 'FViewer'
1>          use 'enum class'

As suggested in the message and on various Stack Overflow questions, changing my code to:

enum class FV_MODE
{
    IDLE,DRAG,ADD_HITBOX,ADD_HURTBOX
};

quickly fixed the problem.

However, I'm still unaware of the differences between the 2 different ways I now know to define enums. Could anybody help clarify for me? And also what makes "enum class" more suitable for managed code?

Thanks in advance,

Guy

Balog Pal
  • 16,195
  • 2
  • 23
  • 37
Guy Joel McLean
  • 1,019
  • 4
  • 12
  • 34

1 Answers1

4

The difference between unmanaged enums and managed enums that makes managed enums more becoming for managed code is that managed enums are managed code and unmanaged enums are unmanaged code. Managed enums can be communicated by the managed code metadata. Unmanaged enums cannot, meaning they may not manifest as part of a managed class.

R. Martinho Fernandes
  • 228,013
  • 71
  • 433
  • 510