> Asserts are made to check for clear incoherent behavior in a library. > Something that just could not happen if the library is coded properly. They > should check for things like function pre/post conditions. They are for > library developers, not end users! > A change in the wire format causing an assert is just not the proper way to > handle the problem, since this is completely unrecoverable on the library > user side. > > This may be generalized to the fact that asserts should not be used for > anything exterior to the library (such as the wire protocol). For instance, > in a file management library, you don't want an assert to be triggered if > there is no space left on the device: you want an error code! I cannot > afford my whole program to crash, just because the broker on the other side > was updated.
Which assertion fails in this case? In which version of lib? - Martin _______________________________________________ zeromq-dev mailing list [email protected] http://lists.zeromq.org/mailman/listinfo/zeromq-dev
