Re: [PATCH+] CLISP support for telent-clx

--=-=-=

Christophe Rhodes <[email protected]> writes:

I made the small error. Patch:


--=-=-=
Content-Disposition: inline; filename=patchfile
Content-Description: patchfile

diff -u -r clx.orig/dependent.lisp clx/dependent.lisp
--- clx.orig/dependent.lisp	2007-01-09 04:56:20.000000000 +0000
+++ clx/dependent.lisp	2007-01-09 04:37:58.000000000 +0000
@@ -1424,7 +1424,7 @@
          (when (or (string= host "")
                    (string= host "unix"))
            ;; ok, try to connect to a AF_UNIX domain socket
-           (sys::make-socket-stream "" display)))))
+           (sys::make-socket-stream "" display))))
     (if socket
         socket
         ;; try to connect by hand
@@ -1435,7 +1435,7 @@
                               "~{~D~^.~}"
                               (rest host))))
               (socket:socket-connect (+ 6000 display) ip
-                                     :element-type '(unsigned-byte 8)))))))
+                                     :element-type '(unsigned-byte 8))))))))
 
 
 ;;; Genera:

--=-=-=



> To explain: the exception for SBCL is because I am involved in SBCL
> development and use CLX with it on a daily basis, and so I am in a
> position to test and verify it there -- I simply don't have time to
> perform release engineering tasks on platforms that I don't use.  If
> you are willing to provide support for clisp, you might wish to make
> simultaneous releases of clx with clisp releases.

I'm also using SBCL but sometimes runing CLISP. clisp-clx will be merged
into main CLISP tree and will be syncronized with main clx tree as often
as possible. 

My oppinion. I think that implementation-oriented development of clx by
splitting it into different implementation-oriented trees across the
world is not good idea. This is unnecessary dispersion of maintainer's
efforts. Some good changes in one tree can be ommited in other. A
structure of CLX allows us to provide implementation-depended part
(small and relatively easy to 
update) and implementation-independed part (which grows these days). But
release announcement policy can be implementation-oriented.

What repository do I need to be oriented: telent or yours? One place for
CLX development would be better, I think.

--=-=-=--


_______________________________________________
Portable-clx mailing list
[email protected]
http://lists.metacircles.com/cgi-bin/mailman/listinfo/portable-clx
See http://www.cliki.net/clx for darcs URL(s)