On Fri, Jan 21, 2011 at 5:34 AM, Jerry James <loganje...@gmail.com> wrote:
> The thing that keeps preventing me from seriously pursuing this is
> actually character and string encodings. ECL is UTF-32 inside, isn't
> it? I don't even know where to start with porting a MULE-inside
> (X)Emacs to a Unicode-inside CL. In the XEmacs code base, we have
> probabilistic character encoding detectors, and so forth, all of which
> would have to be made to work in a Unicode world. It's so daunting
> that every time I think about just experimenting a little with putting
> a CL engine inside, I think about this, and change my mind. :-(
>
What I was suggesting was not replacing (X)Emacs internal structures with
ECL's. That would be foolish. Instead I consider it to be more reasonable an
approach that first links in ECL, exposes (X)Emacs buffers and objects to
ECL, adds an API for Common Lisp programs to manipulate buffers, load files,
and do all that Elisp can do; then add a elisp->CL interpreter and at some
point do the switch.
Juanjo
--
Instituto de Física Fundamental, CSIC
c/ Serrano, 113b, Madrid 28006 (Spain)
http://juanjose.garciaripoll.googlepages.com
------------------------------------------------------------------------------
Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)!
Finally, a world-class log management solution at an even better price-free!
Download using promo code Free_Logger_4_Dev2Dev. Offer expires
February 28th, so secure your free ArcSight Logger TODAY!
http://p.sf.net/sfu/arcsight-sfd2d
_______________________________________________
Ecls-list mailing list
Ecls-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ecls-list
