Message79162
| Author |
lemburg |
| Recipients |
belopolsky, lemburg |
| Date |
2009年01月05日.16:43:57 |
| SpamBayes Score |
0.48213595 |
| Marked as misclassified |
No |
| Message-id |
<496238CC.2070207@egenix.com> |
| In-reply-to |
<4961F708.8080901@egenix.com> |
| Content |
On 2009年01月05日 13:03, Marc-Andre Lemburg wrote:
> Marc-Andre Lemburg <mal@egenix.com> added the comment:
>
> On 2009年01月03日 04:38, Alexander Belopolsky wrote:
>> Alexander Belopolsky <belopolsky@users.sourceforge.net> added the comment:
>>
>> On Fri, Jan 2, 2009 at 10:54 AM, Marc-Andre Lemburg
>> <report@bugs.python.org> wrote:
>>> Marc-Andre Lemburg <mal@egenix.com> added the comment:
>>>
>>> Also note that by removing the extern "C" declarations, you not only
>>> changes the exported symbol names of functions, but also those of
>>> exported globals.
>>>
>> What are " exported globals" other than "exported symbol names of
>> functions"? AFAIK, C++ does not mangle non-function symbols.
>
> GCC doesn't appear to do so, but there's no guarantee that other
> C++ compilers won't touch these symbols:
>
> http://en.wikipedia.org/wiki/Name_mangling
Issue #4846 is a good example of a situation where such name mangling
causes problems even for non-function symbols. |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2009年01月05日 16:43:59 | lemburg | set | recipients:
+ lemburg, belopolsky |
| 2009年01月05日 16:43:58 | lemburg | link | issue4805 messages |
| 2009年01月05日 16:43:57 | lemburg | create |
|