Re: Perl embedding: trial balloon
On 19 Apr 1999 11:51:46 +0200, you said:
#2a (Perl as Emacs module): Nice! I want the module interface to
be
strong enough so that interested third parties can maintain modules
for other languages. However, they should not be bundled or
distributed with emacs as standard.
Is it possible to step back a bit, and define an API that we *can* bundle
with XEmacs, and meet all the languages halfway? Somebody already mentioned
a 'Mule-to-Unicode' conversion function, which both Perl and Tcl 8.1 could
use (plus whatever else uses Unicode).
So - what interfaces would a Perl loadable module need? What would Python
need? What would other languages (Scheme, etc) need?
As was noted already, it *will* get ugly in places (for instance, being
unable to pass (a . b) to Perl). But if we do the groundwork correctly,
we may be able to satisfy *all* the "I want perl/scheme/python/jovial[1]"
queries we see all the time....
/Valdis
[1] Yes, Jovial. ;)
Attachments:
- attachment.sig (application/pgp-signature — 284 bytes)