Newsgroups: comp.lang.lisp
Path: cantaloupe.srv.cs.cmu.edu!bb3.andrew.cmu.edu!nntp.sei.cmu.edu!news.cis.ohio-state.edu!math.ohio-state.edu!cs.utexas.edu!howland.erols.net!vixen.cso.uiuc.edu!uchinews!guppy.cs.uchicago.edu!user
From: alain@cs.uchicago.edu (Alain Aslag Roy)
Subject: Re: Common LISP: The Next Generation
X-Nntp-Posting-Host: guppy.cs.uchicago.edu
Message-ID: <alain-1209961417490001@guppy.cs.uchicago.edu>
Sender: news@midway.uchicago.edu (News Administrator)
Organization: The Anti-Weather Forecasters Coalition
References: <sjpw4hbzvo.fsf@alfresco.usask.ca> <ey3k9udgp7g.fsf@staffa.aiai.ed.ac.uk> <841693608snz@wildcard.demon.co.uk> <joswig-0409960018520001@news.lavielle.com> <842119252snz@wildcard.demon.co.uk> <slrn53cdji.4ub.cbbrowne@wolfe.brownes.org>
Date: Thu, 12 Sep 1996 19:17:49 GMT
Lines: 17

In article <slrn53cdji.4ub.cbbrowne@wolfe.brownes.org>,
cbbrowne@unicomp.net wrote:

> Nothing says that the CGI server must be written in Lisp for you
> to use code written in Lisp.
> 
> Supposing your CGI server enforces (somehow) that your scripts *must*
> be written in Perl, then you can just have the Perl script invoke
> a Lisp program.

Our web server doesn't force scripts to be written in Perl, but some
people here took this exact route for writing some CGIs. Perl handled the
interaction with the web server, then had Lisp do all of the interesting
work. It worked ok, other than the insanely huge size of the Lisp
executables that ACL created.

-alain
