Question in title,
I have seen that there are seemingly global static variables used such as "static enet_uint32 crcTable [256];", "initializedCRC32" (all in packet.c), so a thread-safety concern arises instantly there.
May I ask, are they thread-safe by any means? Do I have to ensure every thread/host has its own crctable and initializedCRC32 ??
(sincerely I have been wondering why these aren't encapsulated in the ENetHost structure itself in first place, seems like a weird design choice to me, somebody explain me sorry...)
Question in title, I have seen that there are seemingly global static variables used such as "static enet_uint32 crcTable [256];", "initializedCRC32" (all in packet.c), so a thread-safety concern arises instantly there. May I ask, are they thread-safe by any means? Do I have to ensure every thread/host has its own crctable and initializedCRC32 ??
Thanks in advance!