socket as int32_t
seanguzz opened this issue · 1 comments
seanguzz commented
Since the host driver has changed the socket to be a int32_t shouldn't the client constructor be changed to take a int32_t as the parameter instead of the uint16_t?
tdicola commented
Oh good catch, yep I missed that while porting over the 1.14 host driver code. Feel free to send a pull to fix it, otherwise I'll look at fixing it later this week.