unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Yuan Fu <casouri@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Calling Lisp in C functions
Date: Fri, 24 Sep 2021 10:55:00 -0700	[thread overview]
Message-ID: <C1443BE6-B9CB-4EBE-B0A0-EAAD0ABFD4B9@gmail.com> (raw)
In-Reply-To: <83r1dfvktm.fsf@gnu.org>



> On Sep 22, 2021, at 11:59 PM, Eli Zaretskii <eliz@gnu.org> wrote:
> 
>> From: Yuan Fu <casouri@gmail.com>
>> Date: Wed, 22 Sep 2021 20:59:00 -0700
>> Cc: Emacs developers <emacs-devel@gnu.org>
>> 
>> I tried to write
>> 
>> ptrdiff_t count = SPECPDL_INDEX ();
>> record_unwind_protect_ptr (ts_delete_cursor, cursor);
>> ...
>> return unbind_to (count, xxx);
>> 
>> But it give a type error, because ts_delete_cursor doesn’t take a void*. I guess I need to define a wrapper function to avoid that error?
> 
> Yes, see for example directory_files_internal_unwind and its usage in
> dired.c.
> 
>> Can I use record_unwind_protect_ptr more than once?
> 
> Yes.
> 
>> What does that count mean?
> 
> It tells unbind_to how much of the unwind-protect stack to unwind.
> See the definition of unbind_to in eval.c.
> 
>> What is specpdl?
> 
> It's an array used for manually managed stack for tracking unwinds and
> other stuff by the Emacs Lisp machine.  See the comments for 'union
> specbinding', starting at line 3135 of lisp.h.

Thanks, I think I know how it works now.

Yuan




      parent reply	other threads:[~2021-09-24 17:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-21 19:38 Calling Lisp in C functions Yuan Fu
2021-09-22  5:45 ` Eli Zaretskii
2021-09-23  3:59   ` Yuan Fu
2021-09-23  6:59     ` Eli Zaretskii
2021-09-23  7:47       ` Andreas Schwab
2021-09-24 17:55         ` Yuan Fu
2021-09-24 17:55       ` Yuan Fu [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=C1443BE6-B9CB-4EBE-B0A0-EAAD0ABFD4B9@gmail.com \
    --to=casouri@gmail.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).