> For more professional looking applications, I've patched CLISP to allow > linking the memfile to the exe file and starting it without a console, see > > http://www.frank-buss.de/lisp/clisp.html > > I've proposed this to the CLISP mailing list for include in the next CLISP > release. > > I think instead of using wxCL it would be interesting to use the low-level > Windows GDI functions and built some framework on top of this. This has the > advantage that you can use every Windows API function, if you like. The > same could be done for Carbon on MacOS X and X11 for Linux. Then you have > the ability to write native applications, which are very close to the > system. > > The API above the system-level could be something like wxCL, but in pure > Lisp. Then it is easy to write starter-kits like Dr Scheme, with rich > libraries and GUI capabilities, see e.g. http://tinyurl.com/9htgs > Nice thingie, sad that it doesn't really work with CFFI. FFI::FOREIGN-CALL-OUT just barfs something about foreign pointers comming from a previous lisp session. Can really advanced FFI stuff (callbacks, multiple libraries loaded when compiling etc.) be saved in memory image at all?
Ignas Mikalajunas _______________________________________________ Gardeners mailing list [email protected] http://www.lispniks.com/mailman/listinfo/gardeners
