[clhp-cvs] CVS update: clhp/TODO

Anthony Ventimiglia aventimiglia at common-lisp.net
Wed Oct 1 19:11:34 UTC 2003


Update of /project/clhp/cvsroot/clhp
In directory common-lisp.net:/tmp/cvs-serv12285

Modified Files:
	TODO 
Log Message:
Beginning tests for CGI package, right now the code in
tests/cgi-test.lisp has to be called interactively, but it does do
some of the job

Date: Wed Oct  1 15:11:33 2003
Author: aventimiglia

Index: clhp/TODO
diff -u clhp/TODO:1.5 clhp/TODO:1.6
--- clhp/TODO:1.5	Wed Oct  1 10:01:47 2003
+++ clhp/TODO	Wed Oct  1 15:11:33 2003
@@ -1,10 +1,14 @@
-$Id: TODO,v 1.5 2003/10/01 14:01:47 aventimiglia Exp $ -*- outline -*-
+$Id: TODO,v 1.6 2003/10/01 19:11:33 aventimiglia Exp $ -*- outline -*-
 
 * Test suite
   Write a test suite, in lisp that will run test on clhp components,
   this will be used during development, to make sure everything is
   working properly.
 
+  This is in thw works is tests/, I think I'll refine it a bit and
+  make it it's own package. There is still more work to be done, and
+  that's a whole different can of beans
+
 * COMPILE-CGI 
   This is just a convenience function that will compile and save fasl
   files with the .clcgi extension.
@@ -18,7 +22,10 @@
   the HTTP headers generated by CLHP.
 
 * TAG
-  This has to be done with a macro.
+  This is pretty nice right now, but I would like to implement it
+  possibly as a reader macro, where something like #<a href="/" #<b
+  "Click Me">> yields <a href="/"><b>Click Me</b></a>. The problem is
+  getting embedded reader macros to work properly.
 
 * Error handling 
   This will be the biggest ongoing project, lets try to create every
@@ -38,10 +45,13 @@
   to be done in CLHP, at least not right away.
 
 * Pre-release check list
-**  version numbering
+**  version numbering    
     VERSION in Makefile and *CLHP-VERSION* in clhp.lisp should be
     set. Eventually I'd like to set up a nice way to have this all
     happen automatically. I think the best way to do this is to make
     the whole build process more lisp dependent. The other option is
-    to go automake with it.
+    to go automake with it. 
+
+    The way it works now is very nice, in fact, I don't think Automake
+    could do it so well.
 





More information about the Clhp-cvs mailing list