Hi ! > I finally decided to give trswm a try and, hah, immediately ran into > problems with autoconf that would be easy to fix in a Makefile but I have > no idea how to fix in an autoconf script and figure most users wouldn't > either be able to do so: the script can't figure out Lua version and fails > (debian has all this lua50, liblua50 and so on).
Well, I'm still an autoconf newbie, but it's never too late to learn :-) My lua detection code was just a cheap hack, it will be cleaned up more sooner than later. BTW, I've just installed lua5 properly, from the package (before that it was installed in my home, and default was lua4), and liblualib.so -> liblualib.so.5 liblualib.so.4 liblualib.so.5 liblua.so -> liblua.so.5 liblua.so.4 liblua.so.5 in /usr/lib What do you have when you do ls -l /usr/lib/*lua* ? > > <http://www.bagley.org/~doug/shootout/> (or maybe they're an extension of > the ones I saw earlier as I can't find anything else) and Lua 4.0 (5.0 > should be more efficient in some aspects) most of the time seems to > perform much better than e.g. Guile. (I don't know which Lisp/scheme/ > whatever sawfish used/s.) Rep. Ok, I'm not claiming WM _is_ rewritten, but I know from experience - if you could quickly prototype something in scripting language, it will very likely stay so, instead of properly coded. Eventually, over time software manages to migrate from nice C code with occassional interpreter calls to one large table of callbacks exported to interpretable code and called from there. Then, you start optimising scripted code for speed, implement precompiling, next is crucial parts of C code are being implemened as a library to chosen language, and suddenly you have fully featured fully scripted system. > -- With all the best, yarick at relex dot ru.
