|
From: | Stephen Leake |
Subject: | Re: Reliable after-change-functions (via: Using incremental parsing in Emacs) |
Date: | Fri, 03 Apr 2020 16:04:04 -0800 |
User-agent: | Gnus/5.13 (Gnus v5.13) Emacs/26.2 (windows-nt) |
Eli Zaretskii <address@hidden> writes: >> From: Stephen Leake <address@hidden> >> >> >> You mention "consing of Lisp objects" above, which says to me that the >> >> text is stored in a more complex structure. >> > >> > I meant the consing that is necessary to make a buffer-substring that >> > will be passed to the parser. >> >> Since are are calling the parser from C (if it is linked into Emacs, or >> in a module), I still don't understand. Does C code have to cons to >> create a string? > > If course. How else do you get a UTF-8 encoded string to pass to the > parser as a copy of buffer text? malloc and memcpy. I guess that's what you mean by "cons"; I was assuming you meant the actual elisp function. -- -- Stephe
[Prev in Thread] | Current Thread | [Next in Thread] |