r8906: fixes for allegro loop, start of lispworks loop - not working

[clsql.git] / ChangeLog

diff --git a/ChangeLog b/ChangeLog
index a0a248b3b90bbc7914e812c06b7d74b57efd54f8..e7b049f51da8744c0a7f91d2e68945e9ee0adb58 100644 (file)
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,27 @@
+09 Apr 2004 Kevin Rosenberg (kevin@rosenberg.net)
+       * Version 2.4.2 released:
+       loop extension now supported on Allegro, all
+       CLSQL-TESTS pass on Allegro.
+       * sql/metaclasses.lisp: Some optimization
+       of compute-slots, be selective when
+       ordered-class-slots needs to be called
+       instead of class-slots
+       * TODO: add URL with documentation on
+       extending Lispworks LOOP form
+       
+09 Apr 2004 Kevin Rosenberg (kevin@rosenberg.net)
+       * Version 2.4.1 released: CLSQL-TESt suite passes
+       all tests for postgresql and CMUCL, SBCL, OpenMCL.
+       Allegro and Lispworks pass all tests except for
+       FDML/LOOP/1 since the loop extension have not yet
+       been ported to those implementions.
+       * sql/metaclasses.lisp: Added new slot to standard-db-class
+       to hold user-specified type. OpenMCL adjustments to compensate
+       for its type-predicate function. Since AllegroCL, Lispworks,
+       and OpenMCL have different slot orders, added compute-slots
+       and ordered-class-slots functions so their slot order matches
+       SBCL/CMUCL.
+
 08 Apr 2004 Kevin Rosenberg (kevin@rosenberg.net)
        * Version 2.4.0 released: All tests for clsql-classic now finish
        correctly on Allegro, Lispworks, CMUCL, SBCL, OpenMCL for