From usocket-devel at common-lisp.net Sat Sep 2 23:21:34 2006 From: usocket-devel at common-lisp.net (usocket) Date: Sat, 02 Sep 2006 23:21:34 -0000 Subject: [usocket-ticket] #6: win32 function name mismatch in clisp and lispworks Message-ID: <080.c50886df77243dfae129061b7cb8bcff@common-lisp.net> #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: usocket usocket From usocket-devel at common-lisp.net Sat Sep 2 23:21:47 2006 From: usocket-devel at common-lisp.net (usocket) Date: Sat, 02 Sep 2006 23:21:47 -0000 Subject: [usocket-ticket] Re: #6: win32 function name mismatch in clisp and lispworks In-Reply-To: <080.c50886df77243dfae129061b7cb8bcff@common-lisp.net> References: <080.c50886df77243dfae129061b7cb8bcff@common-lisp.net> Message-ID: <089.1a5ab78c4adb54adbd74d44ef00ee986@common-lisp.net> #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 Resolution: | Keywords: Patch: 1 | -------------------------+-------------------------------------------------- Changes (by afuchs): * patch: 0 => 1 -- Ticket URL: usocket usocket From usocket-devel at common-lisp.net Sat Sep 9 22:11:47 2006 From: usocket-devel at common-lisp.net (usocket) Date: Sat, 09 Sep 2006 22:11:47 -0000 Subject: [usocket-ticket] Re: #6: win32 function name mismatch in clisp and lispworks In-Reply-To: <080.c50886df77243dfae129061b7cb8bcff@common-lisp.net> References: <080.c50886df77243dfae129061b7cb8bcff@common-lisp.net> Message-ID: <089.2c276f980fde75c23e9bf396841a6081@common-lisp.net> #6: win32 function name mismatch in clisp and lispworks -------------------------+-------------------------------------------------- Reporter: afuchs | Owner: default Type: defect | Status: closed Priority: major | Milestone: release-0.2 Component: tcp-socket | Version: 0.1.0 Resolution: fixed | Keywords: Patch: 1 | -------------------------+-------------------------------------------------- Changes (by ehuelsmann): * resolution: => fixed * status: new => closed Comment: Accepted and resolved this issue: patch applied in r118. -- Ticket URL: usocket usocket