See Perl 6 to machine code via Common Lisp and sbcl:
CommentsKindaPerl6 is a self-compiling compiler written in a subset of Perl 6 with support for multiple emitter backends. [...] now the Common Lisp backend is getting up to speed.
$ sudo port install sbcl
Arc walks the blogosphere again.
The LtU article and comments on programming.reddit.com show that there's still some interest in the topic. Although we have all waited a very long time.
Arc currently powers a spam-filter and Y Combinator's Startup News, some kind of reddit.com clone.
John Wiseman says "I used to think people working on new Lisp-like languages were misguided, but after internalizing the idea that Common Lisp is static, and therefore dead, I'm a lot more sympathetic."
I don't think Common Lisp is really dead. People use it for new projects and new libraries. ASDF wasn't there 10 years ago and all important implementations support it. Many libraries and tools became a de facto standard you can use with your favorite implementation.
Dead relatives shouldn't be the only reason to design a new programming language (or new variation of an existing one).
Paul Graham sure likes Lisp. He wrote books about Common Lisp and his financial success is based on it, too. He doesn't seem to be a language zealot as he speaks positively about Python and uses MzScheme for developing Arc. The Lisp family can be sure to gain a fine, new member. Not a black sheep from "misguided people".
CommentsYou can find some snippets to make Python work with Haskell on PythonVsHaskell.
The code is for Windows, but it shouldn't be difficult to adapt this to Unix.
Finding this on a X vs Y page gives you some hope in humanity again. :-)
In the real world it isn't about which one is the ultimate programming language. When you think beyond this, you can choose more freely and combine the best of all the available tools for the job.
OCaml and Ruby can live together, too.
Even Common Lisp and Java can be used in one project without causing a rift in reality: CLiki page about Java
CommentsIn the second paragraph of the first chapter of Practical OCaml you can read
OCaml is not a popular language in the way that Java is a popular language. Flame wars rarely break out over non-Lisp languages that are not in the mainstream.
I can't describe how proud I am. :-)
CommentsEdi Weitz asked if people would be interested in using Hunchentoot (a web server implemented atop of TBNL) in Common Lisp implementations other than LispWorks.
A few weeks later the Month of the Hunchentoot began. :-)
:-)
Javier asks in his post <1152957974.751393.130630@b28g2000cwb.googlegroups.com> on comp.lang.lisp what's happening to cliki.net. The site is down.
And about two days later there's no information in the newsgroup comp.lang.lisp or on Planet Lisp. No blog mentions anything.
It's like nobody really cares. But cliki.net is heavily used for "Common Lisp's answer to CPAN", ASDF-Install.
I'm guessing there are just some technical problems and danb has enough to do to fix it. So I don't want to critize him or anyone else who is helping to fix the problem, instead of writing about it in his blog or on the news.
But it's still very strange. A central point of the community is out of order. And nobody cares.
That's sad.
CommentsWillem Broekema announced CLPython in his news posting <1152045368.275100.86920@b68g2000cwa.googlegroups.com> today.
That's really crazy shit! (Meant in a good way! :-)
A Python implementation in Common Lisp. At the moment it's Allegro only, but in the future we could perhaps compile CLPython with Python to run Python ... (CMUCL's compiler is called Python, too. :-)
Sound's like fun.
By the way: There's a similar approach called Python-on-lisp. This project uses the real Python and builds a bridge to it.
People use the opportunity to write about their feelings regarding the "Lisp community" in the comments of one reddit.com post.
The post is currently on the front page of reddit.com. And rising.
Current version 0.4.3 of CL-EMB now uses the faster file slurping function from http://www.emmett.ca/~sabetts/slurp.html and got a new template tag @insert
I fixed an example for generator loops in the README
From the NEWS file in the current CVS version of SBCL:
Former Common Lisp figurehead EbOY has switched to WordPress.
I'm awaiting EbOY clones any second now … :-)
One reddit user really had some problems with my last blog entry Don't say "no"!
In the comments on reddit he was obsessed with the four little words "the task at hand". I was giving a bad advice by letting a programmer choose his own tools to do his work.
As if a programmer can't think for himself. When you don't have any additional budget at all and you think Delphi would fit the current problem, then you are out of luck. You have to pay for Delphi. Same goes for some other tools. So you have to find another way to solve your problems.
There's a strictly Java only policy at the shop you are working? Don't waste your time thinking about how cool it could be to quickly code something in Ruby.
But when the only reason holding you back using Common Lisp is the doubt if other programmers could pick up when you leave, or support you in maintaining the code …
Brian Mastenbrook wrote it in "Can someone else work on your code?":
I work with a large Common Lisp codebase at work, and I'm often surprised at how easy it is to maintain and make changes to even the "bad" parts of the code.
And I would go further: It's not only easy to maintain the code, it is also easy to learn by reading and modifying given code.
Set up a working environment and maybe point to Lispbox if they want to try it at home, too. Give them a copy of Practical Common Lisp and a week time and the co-worker or successor will get around the first shock and accept Common Lisp. Don't expect them to love it — so you don't get disappointed for them not getting as excited as you are for the language.
I'm not telling. It's your job. You know the facts and all (or most of) the variables to consider. Not me. Trying to force Common Lisp on you as the perfect tool for every problem doesn't help anybody. Even if it is the perfect tool.
Comments(Based on my posting <2T2radg3IosmNv8%stesch@parsec.no-spoon.de>)
Every now and then I read a Usenet posting or blog entry about the somewhat frightening question from management: "Will someone else be able to work on your Common Lisp code?"
Then most people explain why they had to say "no".
You all know the reasons why they think they have to give this answer. But are the reasons really valid?
I don't think so. It is the job of a programmer to work with different tools. Programming languages are such tools, among others. It is expected that a Java programmer can learn the Eclipse IDE within a few days even if he was a long time user of Netbeans. A programmer has to use many tools he wouldn't choose by himself. Do you think most of them really like writing their e-mails at work with Outlook? :-)
Common Lisp is one of the tools that are available. If you think it fits the task at hand then use it. Chances are good you are no wizard, guru, demi-god. Just a person who does his job. You were able to learn Common Lisp and so should be someone who doesn't have to go through the initial phase of a project in a new language. Everyone following you has better and more books, more libraries, a bigger community — Common Lisp has gained a nice momentum and more and more people use it just for fun and for work. Everyone following you can rely on your code. It is very easy to test and fool around with single functions of your program.
Common Lisp is for the mediocre programmer, too. A programmer bitching about the parentheses and refusing to learn something new or different, isn't a mediocre programmer. He is a bad programmer and a very bad employee. Who wants to employ someone who doesn't want to learn for and on the job? The manager/boss who asks you if someone can pick up or support your work when you choose Common Lisp is the same one who expects his staff to be flexible.
"No, I don't think anybody can be as good and flexible as me." is the answer you give when you say "no".
You all know the essays and rantings of Common Lisp users about how wonderful the language is and that you must one of the top programmers choosing it. They are wrong. All it takes is to be a programmer. Even if you are just mediocre.
OK, some programmers who just do their job don't learn programming languages just for fun. They don't have to be bad ones. Just the typical worker who doesn't want to be bothered with work related stuff after a day's work. It's sad but there are such people in every profession. But it's no reason to believe these people aren't able to learn Common Lisp just because they haven't thought of it themselves.
CommentsLispbox is used by people who want to learn Common Lisp, not how to manage their installation of the IDE and Common Lisp implementation.
So here are the simple steps you have to do if you want to upgrade your Lispbox 0.7 for Windows to GNU CLISP 2.38:
You may want to start (double-click) install.bat inside clisp-2.38 to register the filetypes .fas, .lisp, .mem, etc.
CommentsAs reported by Juho Snellman.
I just released CL-EMB 0.4.1 and
CL-WIKI 0.0.2.
CL-WIKI uses
the latest release 0.6.0 of CL-WHO for which
I've supplied some patches. CL-WHO now can
produce old school HTML. Versions below 0.6.0 just generate XHTML.
There are several wikis for almost every web aware programming language.
Wikipedia has a
List of wiki software.
The sad thing about that list: There's just one wiki engine for
Common Lisp at the moment.
That's why I have started the project CL-WIKI.
Very, very simple at the beginning. But I hope to turn it into a wiki engine that can
compete with the existing ones.
You can help by subscribing to the mailing list
cl-wiki-devel and
discussing the future of CL-WIKI.
*HTTP-ERROR-HANDLER* (defaults to NIL) which canNIL and TBNL takes over. The function could
(defun http-error-handler (code)
"Return content for error output of HTTP error CODE."
(case code
(404 (emb:execute-emb *fnf-error-template*
`(:code 404 :uri ,(tbnl:request-uri))))))
(setf tbnl:*http-error-handler* 'http-error-handler)