You should check out some texts the old Symbolics hardware (google is your friend), which had hardware-support for Lispy stuff.
I would also like to note that recursion is just one way to do stuff in CL. I, for one, do not use recursion for iterating over lists, since I don't really think it is natural to use recursion for anything but recursive datastructures. Also, the list (as you probably know, but some don't) is not the only datastructure being used in Lisp. CL comes with (multi-dimensional) arrays, hash tables, mutable strings, etc.
There is also tail recursion. (That is, some forms of recursion may be translated to iterative constructs by the compiler. This is more common in Scheme, but also done to some degree in CL-compilers.)
I just wanted to point out that while Lisp is just fine for AI, it is a general-purpose language, not a
special-purpose AI-language. You can use it for all kinds of programming. (Ok, so C and Assembler is most practical for systems- and OS-programming. At least on current architectures.)
By the way: Apparently lots of people use Lisp (Common Lisp), but don't tell, because they consider it a competitive advantage, and would rather not that their competitors have the same advantage.
Slashdot Mirror
Also, if your heap isn't fragmented, you can make heap allocation nearly as fast as stack allocation.
You should check out some texts the old Symbolics hardware (google is your friend), which had hardware-support for Lispy stuff.
I would also like to note that recursion is just one way to do stuff in CL. I, for one, do not use recursion for iterating over lists, since I don't really think it is natural to use recursion for anything but recursive datastructures. Also, the list (as you probably know, but some don't) is not the only datastructure being used in Lisp. CL comes with (multi-dimensional) arrays, hash tables, mutable strings, etc.
There is also tail recursion. (That is, some forms of recursion may be translated to iterative constructs by the compiler. This is more common in Scheme, but also done to some degree in CL-compilers.)
I just wanted to point out that while Lisp is just fine for AI, it is a general-purpose language, not a
special-purpose AI-language. You can use it for all kinds of programming. (Ok, so C and Assembler is most practical for systems- and OS-programming. At least on current architectures.)
We heard you the ten first fucking times. Just shut up and don't use Lisp if it hurts you so much. Go with the fucking flow, or whatever.
Of course it does! It has had the ability for quite some time, actually. Check out:
l
http://www.chez.com/emarsden/downloads/coffee.e
Franz has a few listed on their webpage: here.
By the way: Apparently lots of people use Lisp (Common Lisp), but don't tell, because they consider it a competitive advantage, and would rather not that their competitors have the same advantage.
CLISP is alright. It doesn't compile to native code, but it's still very fast. It's at clisp.sourceforge.net, I think.
Isn't FIX that Norwegian gay BBS?
(Not that there's anything wrong with that.)
Perhaps you should know not to enable ECN if you don't know what it is and what the consequences are.
("This looks l33t, I think I'll just enable it. I bet it'll make everything super-fast!")
My buildworld (FreeBSD) is down to about forty minutes now. I'll be happy when it's done in five minutes.