On Wednesday 04 December 2013 00:48:02 William S Fulton wrote:
> On 30/11/13 14:38, Geert Janssens wrote:
> > Within the runtime test, I can only check for Guile < 2.0 to skip
> > the
> > tests. I'm not aware of a way to check for the platform I'm running
> > on and even less so for the compiler used to compile the wrapper
> > code. (This issue is clang only).
> How about trying utsname:sysname -
This was useful, thanks. I have a branch in my personal github repo that fixes the integer test now:
Unfortunately the os x environment on travis seems to be in a flux. I already had some trouble to get guile 1.8 installed (they seem to have switched to guile 2 by default, although it still won't compile). So lots of other tests are now broken. This has nothing to do with the integers test patch though.
I'm not sure how to present this patch for inclusion in the swig master branch. Obviously you don't want to merge the complete guile-osx branch, but the single commit for fixing the integer test on osx would be useful.
The numeric_overload test will have to wait for now. There's a more urgent bug I recently discovered in swig/guile via my work in GnuCash. The string conversions don't work correctly with guile 2 for non-ascii strings. Perhaps guile 1.8 is affected as well, I'm still testing that part.
Are there tests in the test suite specifically targeted at strings (char* ) ? If so, I'll see if it already has a runtime test for guile. I will create one of not, or extend it to test non-ascii strings otherwise.