Previously, event codes without a kernel define would resolve into properly
named objects, e.g. libevdev.EV_REL.REL_0B

This breaks the API whenever the kernel introduces a new define because that
named object will just disappear. e.g. the above REL_0B is now
REL_WHEEL_HI_RES.

Since the undefined names aren't supposed to be used by callers directly
anyway, rename them to be underscored instead: libevdev.EV_REL._REL_0B
This means we can still return them from evbit() and events() but the
underscore signals a private API.

The actual name remains the same, so print(_REL_0B.name) will not have an
underscore. This is to avoid bugs/breakage where the caller uses the 3-lettter
prefix for other purposes.

Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>

Fixes #5

Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>

This makes it easier to determine which one of the codes actually exist and
which ones are just made up because they fit below the respective REL_MAX,
KEY_MAX, ...

Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>

libevdev.evbit('ABS_X') should just work

Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>

Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>

Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>

Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>

Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>