Hi Swig-master,

 

I am having the exact same problems as the person that submitted this defect is having.  I see that the workarounds are to modify the generated code.   The last error is not addressed in the posting, to my knowledge. Does this workaround not defeat the purpose of swig in that swig generates the code for me and I can make minor changes in the API header and just regenerate the extension code?   Do you know when you might have a fix for this version of Ruby?

 

Thanks in advance,

 

Judy Walker