While gian was working on some (still not working) FAQ system a few months ago, I have made a completely new one that should suit our needs.

You can visit it at: http://www.tpu.org/tea/FaqTree./cg-70

Please suggest any questions and answers you think belong, and if your question belongs in a topic that isn't included there, please post here your ideas for topic areas that should be added.

Well done... I think it should be fitting to our purpose.

Nicely done. A few nitpicks, though:

How about a link to it in the navigation at the top of every page?

The answer-approval thing on the front page appears not to work. Perhaps the category needs to be changed?

A link would be good, of course. I was thinking that if some kind person comes up with a shiny layout, we can not bother including it until that is ready. Jim Collins has responded to my post at http://www.teendev.com/ and said that he will try to make a shiny layout. So hopefully that will happen soon!

I had switched up my links for the admin stuff on the front page. You can also approve things from the main FAQ page if you have admin privs, however.

I noticed vladmir_l's comment that compilers consider a program "as a whole." Last time I checked, Lisp compilers compiled incrementally, function by function (so you can do interesting things like replace a function _while the program is running_ which is really nice). Of course, this is just the unknown_lamer being a nitpicker.

unknown_lamer: I don't really know the exact definiation of compiler/interpeter, but wouldn't that be an interpeter, not a complier?

No, because the Lisp compiler compiled code to machine code (some do bytecode like GCL, but most do native machine code). Just because it does it incrementally doesn't make it any less of a compiler. What is really nice is being able to replace functions while the system is running (making Common-Lisp work well in systems that are evolving but need 100% uptime). You can sort of do this in C by compiling modules of the program to different object files, but changing one function in the module requires recompiling the module, relinking, and restarting the program (making the CL way better).