Alastair Robertson

> > I'd also add that `$myenum` should be displayed as a string in `print($myenum)` and `@[$myenum] = $myenum`. It would be a change in behaviour, but I'd say it's...

Enums being usable as integers is pretty much specific to C though. More modern languages mostly have stricter typing on them. BpfScript isn't trying to copy C and I'd say...

It seems that there are two issues here that can be separated: 1. Backwards compatibility 2. Enum type semantics **Backwards compatibility** Since we don't have any concept on an "enum"...

Also, it seems likely that at some point we'll want to let users define and use their own enums in BpfScript, so we'll need to take that into account too.