To make sure that we don't miss anything when we get to refactoring commodule, let's write down everything that we don't like about its current architecture and workings. Things I heard of already:
unsigned int for coordinates induce some hard to find bugs with arithmetic;
reserve()ing std::vector in SDK doesn't work as expected (NULL values or something appear). Why?
due to lack of its own event loop commodule have to be quite smart about what messages may be waiting in the socket, which makes overall process flow quite tangled.
To make sure that we don't miss anything when we get to refactoring commodule, let's write down everything that we don't like about its current architecture and workings. Things I heard of already:
unsigned int
for coordinates induce some hard to find bugs with arithmetic;reserve()
ingstd::vector
in SDK doesn't work as expected (NULL values or something appear). Why?Anything else?