[drakma-devel] CLISP problem with READ-SEQUENCE; patch

[Anton Vodonosov]

Hello.

When using HTTP-REQUEST for non text content types, we
have following error in CLISP:

  SYSTEM::STORE: #\< does not fit into #(0 0 0 0 0 0 0 0 0 0 ...), bad type

  Backtrace:
    0: INVOKE-DEBUGGER
    1: SYSTEM::STORE
    2: EXT:READ-CHAR-SEQUENCE
    3: READ-SEQUENCE
    4: DRAKMA::READ-BODY
    5: DRAKMA::HTTP-REQUEST-FINISH-REQUEST
    6: unwind-protect frame
    7: compiled block frame for HTTP-REQUEST
    8: HTTP-REQUEST

This is because CLISP doesn't support READ-SEQUENCE on
a stream having STREAM-ELEMENT-TYPE == 'CHARACTER.

The patch attached fixes this problem by explicit change
of stream element type in the DRAKMA::READ-BODY function.

Test URLs:
http://www.google.com/calendar/feeds/pm55j8kg30dnm54ib2if9fuocc@group.calendar.google.com/public/basic
http://www.lisperati.com/lisplogo_alien_128.png

Best regards,
-- Anton

-------------- next part --------------
A non-text attachment was scrubbed...
Name: clisp-read-sequence-patch.diff
Type: application/octet-stream
Size: 1172 bytes
Desc: not available
URL: <https://mailman.common-lisp.net/pipermail/drakma-devel/attachments/20080322/7b647048/attachment.obj>