A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from http://mail.python.org/pipermail/python-dev/2002-March/021002.html below:

[Python-Dev] Opinions on const-correctness?

[Python-Dev] Opinions on const-correctness? [Python-Dev] Opinions on const-correctness?Juergen Hermann Juergen Hermann" <j.her@t-online.de
Tue, 12 Mar 2002 21:10:24 +0100
Hi!

When you interface const-correct C or C++ code with Python, you
currently need to jump through hoops like this:

somefunc(const char* modulename, const char* key)
{
    ... PyImport_ImportModule(const_cast<char*>(modulename)) ...


I'd be willing to invest some time to change this, the question is:

 1. someone opposed to such a change?

 2. any technical reasons against it (const is ANSI, do we have a
portability problem that cannot be solved by a #define)?

The largest negative effect I can see is that it'll add some turbulence
to the CVS log (many little changes).

Ciao, J=FCrgen





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