Wiki: extend

- embed

mostly stuff in links such as elk, siod, ecls, librep on lisp side

but playing with more or less extended lisp - eg cl-sdl

and python also

run through possibilities of all approaches

FFI stuff under lisp:

http://xarch.tu-graz.ac.at/autocad/lisp/ffis.html ffis

also http://www.cliki.net/cparse cparse as part of all this

and http://lush.sourceforge.net/index.html LUSH - integrates loads of stuff with basic lisp interpreter (could be useful as testbed - problem with integration is getting right down into our custom file format at low-level ??)

can interface to OpenCV? ([computer vision]?) - currently checking this package out

LUSH? ::

libguile :: (scheme) documentation makes it looks quite easy

siod? :: finally compiled without dbm stuff on fm01 (changed dirent ref to namelen to just strlen(r->d_name)) documentation points to sample.c and siod.c for examples

librep :: to check out: is used by sawmill and jade (editor)

elk? :: (scheme) looks interesting -examples ??

ecls? :: ?? leave it

python :: see gsimca? - need better examples

cl-sdl? / ffi? :: see above

+loads of others: VSlisp/ sizzle (development shifted to guile) + comp vision stuff concerned with extending - such as Envision.

options -

1) deal with embedded scheme or lisp (of which libguile, siod, +(librep) most promising. + also see vslisp? and retrolisp?

2) write own lisp-like language (byte lisp interpreter, abuse-sdl and pico lisp (leave it) as examples. also jlisp but that won't compile (even without dumpexec stuff)

3) bend python towards lisp or use parse?-ing stuff (spark, simpleparse, YAPPS)

see IBM functional programming in python tutorials:

is basically:

a) map, reduce, filter and lambda

b) list comprehensions - for x in list

c) apply:- apply(actions,args)

d) xoltar functional prog toolkit: http://sourceforge.net/projects/xoltar-toolkit/ here

pickle and parser stuff (+ parser module, and PLY)

4) use lisp extended with c functions but main work in lisp ( cl-sdl?)

(also cmucl-xlib-and-gl but can't get that working as problem with xopendisplay)

this approach or extended/embedded scheme/lisp favoured