That would sure be "way nice" for me and my users...
-Dave
----- Original Message -----
From: "Juergen Hermann" <j.her@t-online.de>
To: "Python Developers List" <python-dev@python.org>
Sent: Tuesday, March 12, 2002 3:10 PM
Subject: [Python-Dev] Opinions on const-correctness?
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ürgen
_______________________________________________
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
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