Showing content from http://mail.python.org/pipermail/python-dev/attachments/20091019/d7f6ae05/attachment.htm below:
<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><a href="http://bugs.python.org/issue6952">http://bugs.python.org/issue6952</a><div><br></div><div>Martin v. Löwis suggested that solutions to this issue should be discussed here.</div><div><br></div><div>My goal is to avoid compiler warning and the need to cast to remove const when</div><div>calling the python API.</div><div><br></div><div>For example I see compiler messages like this on Mac OS X Snow Leopard <span class="Apple-style-span" style="font-family: monospace; white-space: pre; ">g++ reports:</span></div><div><font class="Apple-style-span" face="monospace"><span class="Apple-style-span" style="white-space: pre;"><br></span></font></div><div><span class="Apple-style-span" style="font-family: monospace; white-space: pre; ">example.cxx:633: warning: deprecated conversion from string constant to char*</span></div><div><div><br></div></div><div>The patch I developed for comment only adds const to the input parameters and used casts to</div><div>allow output parameters to stay without the const.</div><div><br></div><div>This is because adding the const to the input params will not break existing code, but</div><div>adding const to output parameters may well require code changes for users of the Python</div><div>API.</div><div><br></div><div>What is the best approach to this problem that will be acceptable?</div><div><br></div><div>Barry</div><div><br></div></body></html>
RetroSearch is an open source project built by @garambo
| Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4