Add a layer of abstraction for the script bindings.
commitb1af96c1279f14c9a7fb5040a5f5ae19d1584fb5
authorSadrul Habib Chowdhury <sadrul@users.sourceforge.net>
Thu, 24 Jul 2008 14:53:10 +0000 (24 10:53 -0400)
committerSadrul Habib Chowdhury <sadrul@users.sourceforge.net>
Thu, 24 Jul 2008 14:53:10 +0000 (24 10:53 -0400)
treed26e92fc58511811ac5b24f4111ba5d09ec52932
parentea6735e9eac4a6b09941973a1ec6d33f295aa045
Add a layer of abstraction for the script bindings.
This layer of abstraction will allow to support any number of scripting
languages. Right now the support for scripting is built-in. However, it
won't be very difficult to exclude any built-in scripting support for a
particular language, and use dynamic modules instead.

If we decide that dynamic modules is the way to go, then apart from the
changes required for the build system, the only change in code will be in
script.c:LoadScripts(). There can be multiple modules each supporting a
particular scripting language, and the user will need to explicitly
specify which modules they want to use at start up (e.g., screen -M lua).
This will appease people who do want scripting support, but also people
who don't want it, and don't want the additional bloat.
src/lua.c
src/process.c
src/screen.c
src/screen.h
src/script.c [new file with mode: 0644]
src/script.h [new file with mode: 0644]