CLSQL on ECL

<jhyiugjhvbjh234-JGs/[email protected]> Thu, 23 Aug 2012 13:31:52 +0400
Newsgroups gmane.lisp.clsql.general
Message-ID <[email protected]>
		Hello.
	I am trying to use CLSQL with ECL. I know it is unsupported, but
I am not sure if some of these are worth fixing even without supporting
ECL officially.

	(I do use CLSQL with SBCL succesfully)

	First, I found a clear typo: in sql/db-interface.lisp, 

--- sql/db-interface.lisp
+++ sql/db-interface.lisp
@@ -380,8 +380,8 @@ of TYPE_NAME (keyword) PRECISION SCALE N
 
 (defgeneric db-type-has-auto-increment? (db-type)
   (:method (db-type)
-    (declare (ignore db-type)
-            nil))
+    (declare (ignore db-type))
+            nil)
   (:documentation "NIL [default] if database-type supports auto-incrementing columns."))
 
 ;;; Large objects support (Marc Battyani)

In most implementations it does work and provides correct result, but in
some sense it is accidental.

	Second, it looks like CLSQL uses STANDARD-*-SLOT-DEFINITION, 
which may complain about :db-kind slot initialization option being 
unknown. I do not know MOP well enough to understand how this could be
improved. ECL CLOS implementation does complain, and in such cases ECL
is usually nitpicking but technically correct.
	
	Pure ECL problems, if someone is interested, are:

- generic-function-lambda-list not being a list after 
ensure-generic-function.

- some MOP functions residing in CLOS: package

- getenv living in EXT: instead of FFI:

Thanks