roberts


Group: Members
Posts: 4983
Joined: Oct. 2003 |
 |
Posted: May 10 2008,12:43 |
 |
The only issues I have found are:
1. Fltk menu as already noted. Only concerns two programs, editor.lua and iconView.lua. For the second a work-around is possible. If we have to for go editor.lua for now, then that is OK.
2. Some Lua scripts are using lfs. Personally I don't use lfs, as I have written isDir, readDir, and getDirs using standard Lua and popen (see functions5.lua). So, I am sure that lfs could be dropped and the standard functions be used.
3. We do use Lua sockets. There is no work-around for sockets. So we need to have a lua sockets be able to be "require"d or loadlib'ed.
|