Hrvoje Niksic <hniksic(a)srce.hr> writes:
wmperry(a)aventail.com (William M. Perry) writes:
> Hrvoje Niksic <hniksic(a)srce.hr> writes:
>
> > SL Baur <steve(a)vmailer.xemacs.org> writes:
> >
> > > I have tentatively approved Michael Sperber's plan for addressing
Lisp
> > > Engine updates. As I understand it, it does not involve commitment to
> > > anything specific until all the issues have been hashed out.
> >
> > If it doesn't involve commitment to anything specific, then what is
> > Michael's plan, exactly? I'd like to know what we are agreeing with,
if
> > anything.
>
> I believe the plan was to do something similar to what Perl/Tk does to
> uncouple Tcl and Tk. You'd have a generic scripting language API to
> set/get variables, call functions, etc.
OK, but... I have no idea what Perl/Tk does, really. Uncoupling Emacs
from its current scripting language sounds nice, but is in fact pretty
hard, because the internals are making heavy use of the object system
(Fcons, GC, ...)
One of the bad things about Tk is that down in the guts some things
pretty much have to be Tcl code, even if you are supposedly using it from
C. Perl/Tk (or pTk for portable Tk) changes all the widgets to use generic
TkLangXXX functions instead of TclXXX functions, so that all you have to do
to plug in new languages is create the glue TkLangXXX stuff.
> What would be really cool is to be able to have 2 scripting
> languages loaded at one time. :) Anyone seen the 'perlmacs' patch in
> the perl CPAN archives?
I've seen it, but that hack hasn't gained much popularity, it seems.
Oh, I didn't say it was a good idea, just that it would be cool. :)
-Bill P.