There is now the question, if a alternativ newLISP-TK can be build which use the DLL instead of the EXE. Calling LISP is not the problem, but the EXE version use a callback technik via TCP, where I am not sure if it can be done with the DLL.
For what it can be usable:
For systems without installed TCP-IP stack.
For systems with have security concerns with personal firewalls.
One process solution
That would be possible, you would have to rewrite some routines in newlisp-tk.tcl. I think the potential demand for this is too small. The only ones complaining about tcp/ip are occasional Win95/98 users, and I am not shure if compatibility with those systems is already broken anyway because of shared memory and semaphores in v.8.2.3 and later.
Perhaps GUI work would be better invested building a lisp layer on top of the TK api.
>That would be possible, you would have to rewrite some routines in newlisp-tk.tcl
Can give you a hint, how it can be done? The current EXE can be called and can start actions in TK as a reaction of this call, because the interface transport the call, but does not wait on the answer.The answer comes with a seperate callback from lisp. In the meantime both process run independently. With DLL each call give a return value and is the DLL is then inaktiv until the next call. Here is only one code running, either the MAIN-EXE or the DLL.
>Perhaps GUI work would be better invested building a lisp layer on top of the TK api.
What have you in mind with the lisp layer?
We have the (tk ...) function to create TK-GUI via LISP.
Heeeeeeee I searched for that Library some years ago !! Finaly its possible to
run libs from Tcl ;-) (wasnt possible then..) great thanks for the tips..although Im unable to drop newlisp for tcl :-)