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 developers <emacs-devel@gnu.org>
Subject: Re: Calling Lisp in C functions
Date: Wed, 22 Sep 2021 20:59:00 -0700	[thread overview]
Message-ID: <87357FA2-4AF8-4E7E-BD26-1852D9C8CE6F@gmail.com> (raw)
In-Reply-To: <83y27pw4c3.fsf@gnu.org>



> On Sep 21, 2021, at 10:45 PM, Eli Zaretskii <eliz@gnu.org> wrote:
> 
>> From: Yuan Fu <casouri@gmail.com>
>> Date: Tue, 21 Sep 2021 12:38:21 -0700
>> 
>> What’s the best way to evaluate Lisp or call a Lisp function that could signal in a C function and then free allocated memory? I assume that I can’t just call the Lisp function and hope it doesn’t signal.
> 
> You want to catch the errors in Lisp that you call from C?  If so, use
> the safe_call functions we already have.
> 
> If all you want is make sure memory will be allocated, but don't mind
> if the signal thrown by Lisp gets back to command loop, use
> record_unwind_protect to register a function which will release the
> memory.

Thanks, I still don’t know how does stack works so here’s some naive questions:

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? Can I use record_unwind_protect_ptr more than once? What does that count mean? What is specpdl?

Yuan


  reply	other threads:[~2021-09-23  3:59 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 [this message]
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

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=87357FA2-4AF8-4E7E-BD26-1852D9C8CE6F@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).