Enum versus #define constants: what is the difference?

A strong answer

A strong candidate frames Enum versus #define constants: what is the difference? around the exact memory layout, compiler semantics, and hardware execution model covered in Enumerations and Typedef Abstractions. Explain how enum constants differ from macros in terms of type safety, scope, and debugger visibility.

A developer reading this code must guess what 1, 2, and 3 signify. If someone passes 42, the function fails silently or enters an undefined state.

While macros provide descriptive names, they create other problems:

• No Debugger Visibility: The preprocessor strips macro names before compilation. In GDB or crash dumps, variables display as raw numbers like 2 rather than STATE_CONNECTED.
• No Compiler Switch Checking: If a new state is added, the compiler cannot alert you to unhandled branches in switch statements.
• No Scope or Grouping: Macros are global text substitutions that ignore code blocks.

In a production interview, always connect the specification rule to its concrete runtime consequence: state what lives on the stack versus the heap or static storage segment, how the compiler or operating system validates alignments, lifetimes, and error codes, and what happens under adversarial or boundary inputs (such as zero-length buffers, integer overflow, concurrent mutation, or partial I/O). Backing your explanation with a small trace of register/memory state transitions immediately separates senior systems engineers from candidates who only memorized syntax.

What the interviewer is listening for

• Mastery of core invariant: Assign sequential and custom integer values using C enumerations.
• Mastery of core invariant: Contrast C enum type safety with strongly typed modern languages.
• Mastery of core invariant: Construct aliased types and opaque handles using typedef.
• Hardware and ABI awareness: Explaining how sizes, alignments, calling conventions, or kernel boundaries behave on real 64-bit targets rather than relying on implementation-defined assumptions.
• Defensive engineering: Naming the exact compiler flags (-Wall -Wextra -Werror), static analyzers, or runtime sanitizers (-fsanitize=address,undefined,thread) that verify correctness in CI.

Common mistakes

• Explaining only surface syntax without tracing the underlying memory addresses, ownership lifetime, or kernel/user-space state transitions.
• Assuming undefined behavior (such as signed overflow, uninitialized reads, strict-aliasing violations, or dangling pointers) will "just work" because it passed an unoptimized -O0 debug build.
• Ignoring return codes, partial reads/writes, alignment padding, or cleanup paths when an allocation or syscall fails midway through a function.