[Openmcl-devel] My Experiences going from 0.13.2 to 0.13.4

[Sven Van Caekenberghe]

FYI,

This week I switched from using OpenMCL 0.13.2 to using OpenMCL 0.13.4 
for my current application - a web application that is the 'backend' or 
'manager' application/interface to a dynamic web site, using portable 
allegro serve, lisp server pages and an interface to postgresql.

Defsystem 3.3 interim had problems with provide and require no longer 
coming from ccl, but from cl: this was easy to fix.

Eric Marsden's pg.lisp Postgresql interface 0.14 was using finally do 
in loop while now just finally is accepted.

Portable Allegro Serve's 1.2.12c was using the unix feature which was 
added to OpenMCL so some code suddenly became active - added some (not 
openmcl) to the reader macros did the trick.

On the subject of Portable Allegro Serve: why is ansi loop from the 
portability layer used for openmcl, it seems that openmcl's own loop 
works just as well ?

HTH,

Sven

PS: Writing Web applications using Common Lisp (my development/testing 
environment is Mac OS X, OpenMCL, ILisp and Emacs 21.3.50.1 with Mac 
support - deployment will propably be CMUCL on Linux) is immensely more 
fun than using Java and furthermore, the resulting application is very 
fast (faster than Java that is, without any optimization or type 
declarations! ). Try it, you'll love it.

--
Sven Van Caekenberghe - mailto:sven at beta9.be
Beta Nine - software engineering - http://www.beta9.be
.Mac - svc at mac.com - http://homepage.mac.com/svc


_______________________________________________
Openmcl-devel mailing list
Openmcl-devel at clozure.com
http://clozure.com/cgi-bin/mailman/listinfo/openmcl-devel