[Swig-user] Re2: destructor from ruby

[spam <spa...@ya...>]

> In the case of Xapian, issues like this have been addressed in the
> development series by adding a "Xapian::WritableDatabase::close()"
> method which flushes the database, closes the files, and releases the
> write lock.
>
> I'd expect calling "GC.start" would pick up Ruby objects which had no
> references and release them, which would call the C++ destructor, but it
> doesn't seem to work in my quick test.
>
> So you could try using the development releases of Xapian, or ask on the
> Xapian mailing lists to see if any other Ruby users have encountered
> this issue and found a workaround.

Thanks a lot for this information!
As i have already tried the "GC.start" way and it didn´t work for me, 
too, i will try the close-function; seems like it could do exactly what 
i need.
I will post some short feedback if i succeed in compiling xapian on win 
and this works.
Again, thank you very much.