SL Baur <steve(a)beopen.com&gt; writes: > I've now spent the better part of this week porting my code from 21.1 > to 21.2. The internal interface to XEmacs is way too much of a moving > target for me to consider making this code available primarily as a > module at this time. Note that I was not thinking about making it an independent module (i.e. not part of an XEmacs release). Frankly I think that is unlikely happen soon, because much of the improvement is currently (and in the foreseeable future) in the lowevel stuff. However what I have a mind (as a first step) is that a normal "make/make install" can compile and copy parts of XEmacs as modules. I think your database support would be a good candidate for that. One the makefile hackery for that is in place I don't really see that much difference in maintaining it as a part of XEmacs than be compiled as a module and as one that has to be linked in at "make time". IMO. We need at least one major release with modules at this level before we can think about more loosely coupled stuff.