-
Notifications
You must be signed in to change notification settings - Fork 16
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
[WIP] pingmessage: Add function_map variable #61
base: master
Are you sure you want to change the base?
Conversation
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.
An idea, maybe make a QPingMessage class to move the qt faff to another file and leave a pure c++ file?
That's something that I thought. But having two differents implementation of the same thing will increase the debug/development time. Also, the good point to use the same implementation for Qt and pure-cpp is that we catch a bug for both. |
This new variable will help us to create a better log from all function return the function name and the value on it. Right now this variable can't return pointer types. Signed-off-by: Patrick José Pereira <[email protected]>
Signed-off-by: Patrick José Pereira <[email protected]>
A subclass with the extra functions is still the same implementation. (I guess QPingMessage is not a good recommendation as it would imply QObject inheritance). We can leave it. |
We'll need to subclass all pure c++ classes . |
This new variable will help us to create a better log from all function
return the function name and the value on it.
Right now this variable can't return pointer types.
Signed-off-by: Patrick José Pereira [email protected]