Re: cl-http on LispWorks 4.2

Martin Simmons <[email protected]>
Newsgroups gmane.lisp.cl-http
Message-ID <[email protected]>
>>>>> On Wed, 17 Apr 2002 12:45:07 -0400 (EDT), [email protected] said:

  Greg> CL-HTTP compiles & run OK after disabling LW's default protection of
  Greg> the CLIM package it includes.  I'm not sure about the relative
  Greg> performance yet, though it doesn't seem too much different than under
  Greg> 4.1.  I've not yet experimented with various compiler settings.

Which version of CL-HTTP are you using?  I didn't think anything needed doing
for 70.156, though you probably need to load CLIM before CL-HTTP.


  Greg> There appears to be a significant correspondence between cl-http's
  Greg> CLIM routines & those supplied by LW 4.2.  Are there arguments against
  Greg> using LW 4.2's CLIM routines instead of cl-http's versions?  I think I
  Greg> am sufficiently competent to give that a try, but a hint or two of
  Greg> direction would be much appreciated.

Here is the list of differences that I have found.  It is quite likely that
most of these don't matter (esp. the symbols with no definitions, which
presumably are not used by CL-HTTP).

CL-HTTP CLIM-SYS symbols not exported from CLIM's CLIM-SYS:

MAKE-PROCESS-LOOP 
PROCESS-ACTIVE-P 
PROCESS-DISABLE 
PROCESS-ENABLE 
PROCESS-ITERATE 
PROCESS-KILL 
PROCESS-LOOP 
PROCESS-PRESET 
PROCESS-PRIORITY 
PROCESS-RESTART 
PROCESS-SLEEP 
UNWIND-PROCESS 

CL-HTTP CLIM-SYS symbols with no definitions:

*MULTIPROCESSING-P*
ALLOCATE-RESOURCE
CLEAR-RESOURCE
DEALLOCATE-RESOURCE
DEFGENERIC*
DEFMETHOD*
DEFRESOURCE
MAKE-PROCESS-LOOP
MAP-RESOURCE
PROCESS-ITERATE
PROCESS-LOOP
SETF*
USING-RESOURCE

CL-HTTP CLIM-SYS symbols with different arguments to CLIM's CLIM-SYS:

WITH-RECURSIVE-LOCK-HELD
WITH-LOCK-HELD

-- 
Martin Simmons                            Email: [email protected]
Xanalys Ltd, Barrington Hall,             TEL:   +44 1223 873826
Barrington, Cambridge CB2 5RG, England.   FAX:   +44 1223 873873
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.