[usocket-ticket] #6: win32 function name mismatch in clisp and lispworks
usocket
usocket-devel at common-lisp.net
Sat Sep 2 23:21:34 UTC 2006
#6: win32 function name mismatch in clisp and lispworks
------------------------+---------------------------------------------------
Reporter: afuchs | Owner: default
Type: defect | Status: new
Priority: major | Milestone: release-0.2
Component: tcp-socket | Version: 0.1.0
Keywords: | Patch: 0
------------------------+---------------------------------------------------
some backend/*.lisp files define a remap-maybe-for-win32 function, but use
a remap-for-win32 function. That prevents loading of usocket at least in
lispworks/win32, but I believe it will cause trouble for clisp as well.
Here's a patch that I believe fixes this:
{{{
Index: clisp.lisp
===================================================================
--- clisp.lisp (revision 117)
+++ clisp.lisp (working copy)
@@ -17,8 +17,8 @@
(defparameter +clisp-error-map+
#+win32
- (append (remap-for-win32 +unix-errno-condition-map+)
- (remap-for-win32 +unix-errno-error-map+))
+ (append (remap-maybe-for-win32 +unix-errno-condition-map+)
+ (remap-maybe-for-win32 +unix-errno-error-map+))
#-win32
(append +unix-errno-condition-map+
+unix-errno-error-map+))
Index: lispworks.lisp
===================================================================
--- lispworks.lisp (revision 117)
+++ lispworks.lisp (working copy)
@@ -19,8 +19,8 @@
(defparameter +lispworks-error-map+
#+win32
- (append (remap-for-win32 +unix-errno-condition-map+)
- (remap-for-win32 +unix-errno-error-map+))
+ (append (remap-maybe-for-win32 +unix-errno-condition-map+)
+ (remap-maybe-for-win32 +unix-errno-error-map+))
#-win32
(append +unix-errno-condition-map+
+unix-errno-error-map+))
}}}
--
Ticket URL: <http://trac.common-lisp.net/usocket/ticket/6>
usocket <http://common-lisp.net/project/usocket>
usocket
More information about the usocket-ticket
mailing list