-
Notifications
You must be signed in to change notification settings - Fork 197
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix #204 #205 #207 #206
base: develop
Are you sure you want to change the base?
fix #204 #205 #207 #206
Conversation
pavel-orekhov
commented
Jan 29, 2018
- add message::operator<< for message (AKA append) and for frame
- tests for new methods
- fix indent
* add message::operator<< for message (AKA append) and for frame * tests for new methods * fix indent
part 2: exception at loop.start() part 3: socket is not removed from items_ via separate cb for close() * testcases for it
Issue 207: stack overflow (segmentation) in loop.remove(raw_fd) in loop/raw_fd handler
@@ -125,18 +127,18 @@ namespace zmqpp | |||
void update(); | |||
}; | |||
|
|||
typedef std::pair<zmq_pollitem_t, Callable> PollItemCallablePair; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
does changing these types break api backward compatibility?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think no. it's private type. But size of class will be changed, so recompile of clients is required.
bluca, please say me what is better:
- register onAfterRemove callback at add() time
- register onAfterRemove callback at remove() time
First method is implemented now. But second seems more clean for user and more simple to implement.
*/ | ||
void add(socket_t& socket, Callable callable, short const event = poller::poll_in); | ||
void add(socket_t& socket, Callable callable, short const event = poller::poll_in, Callable after_remove_cb = Callable(nullptr)); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
will this break ABI?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes. Method's name will be mangled differently. Clients of libzmqpp need to be recompiled. But no changes at source code of clients.