John Tobey <jtobey(a)channel1.com> writes:
Judging by a brief look at the XEmacs source, a Perl embedding will
not be too difficult, but before I decide whether to work on one, I
want to propose some extensions to the XEmacs API.
How easy is to introduce new types in Perl (or should I say perl)? In
standard Emacs you can get away without out it but in XEmacs you
really read a character type or better a string type that can contain
Mule strings... Note that you can crash XEmacs by polluting the buffer
with illegally encoded multibyte characters. Recoding everything when
calling perl seems a bit over done. Without access to strings and
buffers it doesn't make much sense.
I presume you already had to introduce perl types for markers and such?
Do the perl reference counting and the elisp garbage collector know
about each other?
As for getting it into mainstream XEmacs, how general would it be?
Would somebody be able to put in say a Python binding or even a clisp
binding instead? Have you looked at the XEmacs loadable modules in
21.2.x? It would be nice for maintainability if one could make
Perlemacs just a loadable module (after a providing some services like
the type extensions in
the core maybe).
Jan