common-lisp/sbcl.sbcl
1
0
Fork 0
mirror of git://git.code.sf.net/p/sbcl/sbcl synced 2026-09-10 07:26:40 -04:00
Code Issues Actions 8 Packages Projects Releases Wiki Activity

Update manual entry for Lisp as a Shared Library.

Browse source 
It's fine to call into Lisp from multiple foreign threads.
This commit is contained in:
Charles Zhang 2021-10-25 17:46:14 -07:00
parent 5cc942300e
commit fe902708cd
1 changed files with 3 additions and 7 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

10
doc/manual/ffi.texinfo
View file

@ -1081,14 +1081,10 @@ it exposes the symbol @code{initialize_lisp} which can be used in
conjunction with a core initializing global symbols to foreign callables
as function pointers and with object code allocating those symbols to
initialize the runtime properly. The arguments to @code{initialize_lisp}
are the same as the arguments to the main @code{sbcl} program.
are the same as the arguments to the main @code{sbcl}
program.
While standalone C code can call exposed Lisp functions which spawn Lisp
threads after the runtime has been initialized, it is currently not
advised to call into Lisp this way from separate C threads running
concurrently.
Note: There is also currently no way to run exit hooks or otherwise undo
Note: There is currently no way to run exit hooks or otherwise undo
Lisp initialization gracefully from C.
@node Step-By-Step Example of the Foreign Function Interface