Re: [Swig-user] wrapper compiler warnings

[William S F. <ws...@fu...>]

Bob Rossi wrote:
> Hi,
> 
> I get these compiler warnings in my python generated wrapper files.
> 
>   foo_wrap.cxx: In function ‘const char* SWIG_UnpackData(const char*, void*, size_t)’:
>   foo_wrap.cxx:659: warning: conversion to ‘unsigned char’ from ‘int’ may alter its value
>   foo_wrap.cxx:661: warning: conversion to ‘unsigned char’ from ‘int’ may alter its value
>   foo_wrap.cxx:666: warning: conversion to ‘unsigned char’ from ‘int’ may alter its value
>   foo_wrap.cxx:668: warning: conversion to ‘unsigned char’ from ‘int’ may alter its value
>   foo_wrap.cxx: In function ‘PyTypeObject* _PySwigObject_type()’:
>   foo_wrap.cxx:1843: warning: missing initializer for member ‘_typeobject::tp_version_tag’
>   foo_wrap.cxx: In function ‘PyTypeObject* _PySwigPacked_type()’:
>   foo_wrap.cxx:2018: warning: missing initializer for member ‘_typeobject::tp_version_tag’
>   foo_wrap.cxx: In function ‘void SWIG_Python_SetModule(swig_module_info*)’:
>   foo_wrap.cxx:2513: warning: unused variable ‘swig_empty_runtime_method_table’
>   foo_wrap.cxx: In function ‘int SWIG_AsVal_double(PyObject*, double*)’:
>   foo_wrap.cxx:2822: warning: conversion to ‘double’ from ‘long int’ may alter its value
>   foo_wrap.cxx: In function ‘PyTypeObject* swig_varlink_type()’:
>   foo_wrap.cxx:3657: warning: missing initializer for member ‘_typeobject::tp_version_tag’
>   foo_wrap.cxx: In function ‘PyObject* PyInit__foo()’:
>   foo_wrap.cxx:3807: warning: missing initializer for member ‘PyModuleDef_Base::m_init’
>   foo_wrap.cxx:3807: warning: missing initializer for member ‘PyModuleDef_Base::m_index’
>   foo_wrap.cxx:3807: warning: missing initializer for member ‘PyModuleDef_Base::m_copy’  
> 
> I'm using python 3.1.2 and g++4.4.1. Are these known issues? Are they safe?
> 
We try and keep the code warning free, but the compiler and python code 
keeps changing. If you have fairly strict compiler warnings turned on 
you are more likely to get warnings like the above. Post your gcc 
compiler warning flags being used and I'll take a look.

William