-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
warnings during compile of pyzmq #78
Comments
I asked that this be filed here because the warning is coming from the zmq header files. |
Aren't you forward declaring zmq_errno(void) and zmq_stopwatch_start(void) incidentally? |
I will check on this... |
I don't think we are forward declaring these. What makes you think that? |
It seems that this particular warning is caused by mixing foo() and foo(void) declarations. The explanation seems plausible as the two functions complained about are exactly those that have no arguments. |
I just looked and we are following the foo() convention that is in the main header files of zeromq. Should we change this or do you think this would be resolve by a change in zeromq itself? |
No. It should be the same at both places. More investigation needed... |
The problem may be that foo() in C is a different prototype than foo() in C++. Can you point me where the forward declaration in pyzmq is? |
We don't really forward declare C functions in pyzmq. We simply include the zmq header file and use the functions. The stuff that appears here: http://github.com/zeromq/pyzmq/blob/master/zmq/_zmq.pxd#L68 Is not used in any way in the generate C code. It just serves as a hint to the Cython compiler so it can get the types correct. |
Maybe cython transleates foo() in pxd file into foo(void)... Anyway the simplest way to check whether that's the problem would be to change two prototypes in zmq.h (zmq_errno() => zme_errno(void) etc.) and see whether the warnings go away. Can you do that for me? |
Yep i will have a look. |
This seems to be fixed. |
Backport of test_last_endpoint shutdown fix, resolves LIBZMQ-462
zre_interface only destroy context if it created it
I was asked by the pyzmq developer to file this ticket with you.
ubuntu 10.4.1. zeromq 2.0.9
The text was updated successfully, but these errors were encountered: