Lisp HUG Maillist Archive

Threads and FFI-calls

hei,

I have an app that is started in a separate thread via 
mp:process-run-function from the lispworks IDE.  The hope is
that I can test and experiment with this app from the IDE
while it is running.  The input-loop is on the c-side and it
seems that while the app is on the c-side the entire IDE is
locked up.  This is unfortunate.

Is there a way to handle this call to the input-function
(which must be on the c-side) which allows the rest of the 
IDE to be responsive? 

(I use linux lispworks personal)

-- 
------------------------------------------------------------------
Stig Erik Sandoe     stig@ii.uib.no    http://www.ii.uib.no/~stig/

Re: Threads and FFI-calls

>>>>> "Stig" == Stig E Sandoe <stig@ii.uib.no> writes:

    Stig> hei, I have an app that is started in a separate thread via
    Stig> mp:process-run-function from the lispworks IDE.  The hope is
    Stig> that I can test and experiment with this app from the IDE
    Stig> while it is running.  The input-loop is on the c-side and it
    Stig> seems that while the app is on the c-side the entire IDE is
    Stig> locked up.  This is unfortunate.

    Stig> Is there a way to handle this call to the input-function
    Stig> (which must be on the c-side) which allows the rest of the
    Stig> IDE to be responsive?

    Stig> (I use linux lispworks personal)

You could use CORBA or some other IPC mechanism to put the C component
in another process.

__Jason
Updated at: 2020-12-10 09:01 UTC