Different behavior of SWIG versions about enum

classic Classic list List threaded Threaded
3 messages Options
Zm
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Different behavior of SWIG versions about enum

Zm
This post has NOT been accepted by the mailing list yet.
This post was updated on .
Why enumerations wrapped by SWIG 2.0.1 and 3.0.12 in two different types?
I mean enums like this:

enum forExample
{
    buba = 'b'
    kiki= 'k'
    etc
}

(Previous version converts it into ints and next version wrap enum to char constants.)
And how to fix it in version 3.0.12?

Zm
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Different behavior of SWIG versions about enum

Zm
This post has NOT been accepted by the mailing list yet.
This bug already appears in SWIG-1.3.29: https://sourceforge.net/p/swig/bugs/665/. I can't understand why nobody doesn't know about this bug. It's very important thing!!!
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Different behavior of SWIG versions about enum

johonde
This post has NOT been accepted by the mailing list yet.
In reply to this post by Zm
Huh! I'm trying to do the same thing on Python and get this bug. May be it is echo of elder bugger sources? And, what is amazing, there are no information about it in SWIG Docs. It is strange guy, it's strange...
Loading...