close Warning: Can't synchronize with repository "(default)" (Couldn't open Subversion repository /project/usocket/svn: SubversionException: ("Can't open file '/project/usocket/svn/format': Permission denied", 13)). Look in the Trac log for more information.

Opened 8 years ago

Closed 8 years ago

#6 closed defect (fixed)

win32 function name mismatch in clisp and lispworks

Reported by: afuchs Owned by: default
Priority: major Milestone: release-0.2
Component: tcp-socket Version: 0.1.0
Keywords: Cc:
Patch included: yes

Description

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+))

Change History (2)

comment:1 Changed 8 years ago by afuchs

  • Patch included set

comment:2 Changed 8 years ago by ehuelsmann

  • Resolution set to fixed
  • Status changed from new to closed

Accepted and resolved this issue: patch applied in r118.

Note: See TracTickets for help on using tickets.