Re: Beware of modules.
On Fri, Jan 15, 1999 at 10:37:28PM +0100, Olivier Galibert wrote:
On Fri, Jan 15, 1999 at 01:26:18PM -0800, J. Kean Johnston wrote:
> So I guess the answer to OG's question is a resounding "YES", we will
> "plug into C code".
Which means that we're going to have compatibility problems each time
we change something in the internal C interfaces. This is already a
terrible pain for the lisp code, and you want to extend that to the C
code?
Do you realize that if external third party C modules become the rule,
we can't change anything to the Mule implementation or the lisp
system? That we couldn't have ported to win32? That the "gung ho"
changes would have been impossible to make?
Not so. If we change things
fundamentally in XEmacs, we simply bump the
version number in the module code, and it will refuse to load modules
that were compiled before that version. I explained this all in a previous
message, but thats how we cope with THAT. Its not a show-stopper. If you
try to load an old module you will get a message telling you you can't.
Look at line 350 of emodules.c.
--
J. Kean Johnston | "If equal affection cannot be,
Engineer, SPG | let the more loving one be me" - W.H. Auden
Santa Cruz, CA +----------------------------------------------------------
Tel: 831-427-7569 Fax: 831-429-1887 E-mail: jkj(a)sco.com