I chose to go with static approach instead of moving them to ENET_IMPLEMENTATION, because it seems like these are intended to be visible to the user of the library as convenient constants they're allowed to use, and therefore, wont break backwards compatibility.
This fixes issue #29.
I chose to go with
static
approach instead of moving them toENET_IMPLEMENTATION
, because it seems like these are intended to be visible to the user of the library as convenient constants they're allowed to use, and therefore, wont break backwards compatibility.