emacs-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Dynamic loading progress


From: Stephen Leake
Subject: Re: Dynamic loading progress
Date: Fri, 13 Feb 2015 15:48:07 -0600
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/25.0.50 (windows-nt)

Daniel Colascione <address@hidden> writes:

> On 02/13/2015 07:01 AM, Eli Zaretskii wrote:
>>> Date: Fri, 13 Feb 2015 04:17:17 -0800
>>> From: Daniel Colascione <address@hidden>
>>> CC: address@hidden
>>>
>>> That's why this whole module effort is misguided and dangerous. With a
>>> CFFI-style approach to loading code dynamically, shared modules don't
>>> need to know anything about Emacs internal structure, so there are no
>>> ABI or source compatibility issues.
>>>
>>> I still think a CFFI port would be less work than trying to extract a
>>> stable Emacs internals API that modules can include.
>> 
>> I don't understand how CFFI would solve the problem, at least not all
>> of it.  We'd still need to write code to allow modules create Lisp
>> objects, right?  That code would still be Emacs version dependent,
>> right?  What am I missing?
>
> In a CFFI world, modules don't know about lisp at all. Lisp code
> describes the signatures of functions in loaded modules and calls into
> the automatically generated wrapper functions. The called code has no
> idea it's being called from lisp. 

Which means (I think), that module code cannot call lisp functions.

My use case requires calling lisp functions; in particular,
put-text-property, but also other higher-level lisp functions in
ada-mode.

I need a compiled module to implement an LALR parser for the Ada
language that is fast enough for very large files.

-- 
-- Stephe



reply via email to

[Prev in Thread] Current Thread [Next in Thread]