Message203118
I get the same warning on Fedora 19.
However, the signature of dbmopen_impl is generated by argument clinic, so it isn't simply a matter of patching the signature in place. I'm also inclined to consider the *platform* header to be wrong, since the dbm_open API really should be accepting "const char *" rather than "char *".
We should find a way to silence the warning to avoid the false alarm in the build output (a cast to "char *" with a reference to this issue would be the brute force approach), but propagating the incorrect type declaration higher up the call stack is unlikely to be the right approach. |
|
Date |
User |
Action |
Args |
2013-11-17 05:45:09 | ncoghlan | set | recipients:
+ ncoghlan, larry, vajrasky |
2013-11-17 05:45:09 | ncoghlan | set | messageid: <1384667109.52.0.185825887111.issue19296@psf.upfronthosting.co.za> |
2013-11-17 05:45:09 | ncoghlan | link | issue19296 messages |
2013-11-17 05:45:08 | ncoghlan | create | |
|