I've ended up deciding to go with Guile via a shell, at least for the time being. Here is my glue code. Guile meets my criteria of being installable as a debian package, having good performance, being stable and actively maintained, supporting data structures, and having simple syntax.
Although I think the possibility of a Trojan horse attack using Guile code embedded in a document is realistically a little remote due to my small user base plus sociological factors, I'm looking into how to sandbox Guile. Guile has a sandbox mechanism that seems to be only focused on preventing excessive use of resources. I've posted on the guile-user email list to ask if there's any way to prevent code from accessing the file system and such. I could also just turn off Guile extensions by default.
In reply to Re: Extending a perl program with Scheme, Lua, or JS
by bcrowell2
in thread Extending a perl program with Scheme, Lua, or JS
by bcrowell2
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |