[issue4846] Py_UNICODE_ISSPACE causes linker error
Marc-Andre Lemburg
report at bugs.python.org
Mon Jan 5 17:44:56 CET 2009
Marc-Andre Lemburg <mal at egenix.com> added the comment:
On 2009-01-05 17:09, Atsuo Ishimoto wrote:
> New submission from Atsuo Ishimoto <ishimoto at gembook.org>:
>
> When I use Py_UNICODE_ISSPACE() in my C++ extension, I got following error.
>
> test.obj : error LNK2019: unresolved external symbol
> "__declspec(dllimport) unsigned char const * const _Py_ascii_whitespace"
> (__imp_?_Py_ascii_whitespace@@3QBEB) referenced in function "struct
> _object * __cdecl fff(struct _object *,struct _object *)"
> (?fff@@YAPAU_object@@PAU1 at 0@Z)
>
> Py_ascii_whitespace defined in unicodeobject.h should be enclosed by
> 'extern "C" {' block for C++ support.
Agreed. There already is such a block in unicodeobject.h, so perhaps
a little rearranging could do the trick.
----------
nosy: +lemburg
_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue4846>
_______________________________________
More information about the Python-bugs-list
mailing list