Re: Starting work on a Java version of Metakit

My goals are
 1) fix the current wrappers
 2) migrate to swig.  I have been using swig for a production python
environment for a year now, and have been very happy.  It is a big job
though.  Swig is a two part process but can mostly use the direct c++
header files for the first pass.

I just realized that my apps just hold onto a single metakit storage
per thread and don't let it go, so that explains why the reference
leaks don't bother me.


Brian
_____________________________________________
Metakit mailing list  -  [email protected]
http://www.equi4.com/mailman/listinfo/metakit