[rdnzl-devel] Re: rdnzl, multiprocessing, Allegro, windows, locking
Edi Weitz
edi at agharta.de
Sun Oct 15 11:43:20 UTC 2006
On Sat, 14 Oct 2006 15:53:08 -0700, "Richard Fateman" <fateman at cs.berkeley.edu> wrote:
>> I think that's a problem related to the IDE and not to RDNZL. In
>> LispWorks 5.0, for example, if I start the apropos example coming
>> with RDNZL (which also uses Application.Run) with
>> MP:PROCESS-RUN-FUNCTION as suggested in the RDNZL documentation it
>> runs fine without locking the IDE, i.e. I can still use the
>> listener or other graphical tools while the .NET window is up and
>> interacting.
>
> I just tried the Apropos example on Allegro... whether started off
> in an emacs buffer or a console window or an IDE debug window. In
> each environment, whether just typed in or within a
> (mp:process-run-function ...) the listener is locked..
OK, so I tried with Corman Lisp 3.0 (using CREATE-THREAD) - no
problems, no locking, like with LispWorks. Maybe someone on this list
can try the same with ECL, so we've covered all Lisps on Windows with
MP capabilities.
> I got a response from Charley Cox that suggests another route is
> needed around this, or I guess I will just have to consider changing
> my model of how to program.
Yeah, or you change your Lisp implementation... :)
More information about the rdnzl-devel
mailing list