16 ms·
for now I have a system that has been successfully using it for weeks, so I pretty think it works. And yes I have watched the code and found a bug. The clock u
by julie1 13y ago
for now I have a system that has been successfully using it for weeks, so I pretty think it works.
And yes I have watched the code and found a bug. The clock used in python is mononotonic but may change its frequency and the the time structure is wrong on 64bits architecture there is a cast to signed long long where it should be unsigned long long.
So if I can find stuff easily and see bugs, it means to me the code is well architectured and readable.
- SamReidHughes 13y agoI know somebody who's dealt with it for a lot more than weeks, and according to him and from what he's shown me the code inside of it and the bugs it has are pretty laughable.
- julie1 13y agoThe real ugly truth is all of our code (mine included) is pretty laughable and bugged. But I made no actual asynchronuous messaging system that actually can send messages with a 99.999% reliability, and hardly no noticeable memory leaks. So since I haven't coded any better, given that it works and suits my need, I use it. And since my code is almost correct (okay, there are places where I wish to use an obfuscator to hide the hideous), replacing zmq with something else, should be quite easy.
- mihai_ionic 13y agoC++ has <chrono>, which guards against this kind of mistake by using the type system.