I don't follow OpenMCL / CCL or Lispworks closely so maybe their is no longer a need to differentiate between 64-bit and non-64-bit fasls. If there is, then shouldn't the definition of lisp-version-string look more like the one below?
thanks
(diff -u this time! <smile>)
Index: swank-loader.lisp =================================================================== RCS file: /project/slime/cvsroot/slime/swank-loader.lisp,v retrieving revision 1.88 diff -u -w -r1.88 swank-loader.lisp --- swank-loader.lisp 17 Aug 2008 08:31:17 -0000 1.88 +++ swank-loader.lisp 11 Sep 2008 13:18:52 -0000 @@ -58,10 +58,16 @@ :sparc64 :sparc :hppa64 :hppa))
(defun lisp-version-string () - #+(or openmcl cmu) (substitute-if #_ (lambda (x) (find x " /")) + #+cmu (substitute-if #_ (lambda (x) (find x " /")) (lisp-implementation-version)) - #+(or cormanlisp scl sbcl ecl) (lisp-implementation-version) - #+lispworks (lisp-implementation-version) + #+openmcl (format nil "~a~a" + (substitute-if #_ (lambda (x) (find x " /")) + (lisp-implementation-version)) + #+ppc64-target "-64bit" + #-ppc64-target "") + #+lispworks (format nil "~A~@[~A~]" + (lisp-implementation-version) + (when (member :lispworks-64bit *features*) "-64bit")) #+allegro (format nil "~A~A~A" excl::*common-lisp-version-number* @@ -69,7 +75,9 @@ (if (member :64bit *features*) "-64bit" "")) #+clisp (let ((s (lisp-implementation-version))) (subseq s 0 (position #\space s))) - #+armedbear (lisp-implementation-version)) + #+(or armedbear cormanlisp ecl scl sbcl) + (lisp-implementation-version) + )
(defun unique-dir-name () "Return a name that can be used as a directory name that is
-- Gary Warren King, metabang.com Cell: (413) 559 8738 Fax: (206) 338-4052 gwkkwg on Skype * garethsan on AIM
On Thu, 11 Sep 2008 09:20:39 -0400, Gary King said:
I don't follow OpenMCL / CCL or Lispworks closely so maybe their is no longer a need to differentiate between 64-bit and non-64-bit fasls. If there is, then shouldn't the definition of lisp-version-string look more like the one below?
Why associate this with the version string rather than the arch string?
LispWorks doesn't need it to keep the fasls separate, because they use different extensions, though it won't do any harm.
__Martin