- flexi-streams-devel@lists.common-lisp.net

[flexi-streams-devel] UNREAD-BYTE and PEEK-BYTE on IN-MEMORY-INPUT-STREAM
by Daniel Oliveira 12 Dec '10

12 Dec '10

Hello, i'm using FLEXI-STREAMS and i have a problem, UNREAD-BYTE and PEEK-BYTE aren't defined for IN-MEMORY-INPUT-STREAM's, is there a reason why they can't be or why it doesn't make sense for them to be?

2 1

[flexi-streams-devel] Flexi-streams problem with SBCL 1.0.34
by Fred Gibson 07 Jan '10

07 Jan '10

I found a problem with the flexi-streams:string-to-octets function. I was getting the following back-trace when using it: (ironclad:make-hmac (string-octets key) :sha1) from zs3:make-digester gives: The value #(55 98 50 52 104 75 97 65 50 54 ...) is not of type (SIMPLE-ARRAY (UNSIGNED-BYTE 8) (*)). [Condition of type TYPE-ERROR] Restarts: 0: [DEFAULT-DEBUGGER] Use default debugger. 1: [ABORT] Return to SLIME's top level. 2: [TERMINATE-THREAD] Terminate this thread (#<THREAD "repl-thread" RUNNING {ACA40D1}>) Backtrace: 0: ((SB-PCL::FAST-METHOD SHARED-INITIALIZE :AFTER (IRONCLAD::HMAC T)) #<unavailable argument> #<unavail.. Locals: SB-DEBUG::ARG-0 = 10 SB-DEBUG::ARG-1 = :<NOT-AVAILABLE> SB-DEBUG::ARG-2 = :<NOT-AVAILABLE> SB-DEBUG::ARG-3 = #<HMAC(SHA1) {F0DD561}> SB-DEBUG::ARG-4 = :<NOT-AVAILABLE> 1: ((LAMBDA (SB-PCL::|.P0.| SB-PCL::|.P1.| SB-PCL::|.P2.|)) #<unavailable argument> #<unavailable argum.. Locals: SB-DEBUG::ARG-0 = :<NOT-AVAILABLE> SB-DEBUG::ARG-1 = :<NOT-AVAILABLE> SB-DEBUG::ARG-2 = :<NOT-AVAILABLE> zs3's string-octets uses flexi-streams:string-to-octets The workaround I'm using for now is instead going to acl-compat's string-to-octets function from acl-excl.lisp: (defun string-to-octets (string &key (null-terminate t) (start 0) end mb-vector make-mb-vector? (external-format :default)) "This function returns a lisp-usb8-vector and the number of bytes copied." (declare (ignore external-format)) ;; The end parameter is different in ACL's lambda list, but this ;; variant lets us give an argument :end nil explicitly, and the ;; right thing will happen (unless end (setf end (length string))) (let* ((number-of-octets (if null-terminate (1+ (- end start)) (- end start))) (mb-vector (cond ((and mb-vector (>= (length mb-vector) number-of-octets)) mb-vector) ((or (not mb-vector) make-mb-vector?) (make-array (list number-of-octets) :element-type '(unsigned-byte 8) :initial-element 0)) (t (error "Was given a vector of length ~A, ~ but needed at least length ~A." (length mb-vector) number-of-octets))))) (declare (type (simple-array (unsigned-byte 8) (*)) mb-vector)) (loop for from-index from start below end for to-index upfrom 0 do (progn (setf (aref mb-vector to-index) (char-code (aref string from-index))))) (when null-terminate (setf (aref mb-vector (1- number-of-octets)) 0)) (values mb-vector number-of-octets))) which seems to work fine. My best, Fred Gibson Founder / Software Developer http://www.streamfocus.com (c)2010 Organon Technologies LLC

2 3

Re: [flexi-streams-devel] a patch for chineses's cp936(gbk) encoding support.
by Edi Weitz 29 Oct '09

29 Oct '09

On Thu, Oct 29, 2009 at 3:17 PM, jingtao xu <jingtaozf(a)gmail.com> wrote: > hi,Edi Weitz: > Because i want to use drakma as my web development tool,but it use > flexi-streams and could not decode chinese's cp936 characters,so i make a > patch to flexi-streams. > > The sbcl has supported cp936(by files supported by beinghe,which cvs path > is:sbcl/src/code/external-formats/enc-cn.lisp,enc-cn-tbl.lisp). i use file > enc-cn-tbl.lisp here. > > The patches is make by following commands: > diff -urN ~/.sbcl/site/flexi-streams-1.0.7/ ~/Downloads/flexi-streams/ >>flexi-streams-cp936.patch > > I send you both the patch files and the patched codes. > The test codes is added and passed. > The documention is updated. [I've put the mailing list on Cc where I think we should continue this.] First of all, I'd be happy to include this into the flexi-streams distribution. There are a couple of issues with the patch, though. What I saw from briefly looking at it: 1. There are several new functions and macros which don't have a documentation string. 2. There are tabs in the files and sometimes the indentation seems wrong. 3. There are parts of the code which are commented out. If they aren't used, they shouldn't be in there. 4. There's at least one file (seems like a variant of the ASDF system definition) which shouldn't be in there at all. 5. The link in the HTML documentation is wrong. 6. Isn't get-multibyte-mapper the wrong name? You don't get the mapper, do you? 7. And the function itself looks like Scheme to me. I think it'd be easier to understand using normal iteration. 8. I don't understand why the encoding factor is 1.5. Is the comment correct or just copied? 9. I'm not familiar with CP936. Is it correct that there's only a big-endian version? 10. One of the new files contains DOS line endings. There's probably more. If you could go over these and send a cleaned-up version of the patch, I'll review it. FWIW, here are some guidelines: http://weitz.de/patches.html Thanks, Edi.

1 0

[flexi-streams-devel] FLEXI-STREAMS::WRITE-SEQUENCE* and CCL
by Ron Garret 14 Jul '09

14 Jul '09

Not sure if this is a Drakma problem or a Flexi-streams problem, but I thought I'd start here. I'm trying to run Drakma on Clozure Common Lisp and I get this when I try to call http-request: > Error: There is no applicable method for the generic function: > #<STANDARD-GENERIC-FUNCTION FLEXI-STREAMS::WRITE-SEQUENCE* #x3000422E84EF> > when called with arguments: > (#<EXTERNAL-FORMAT (:ISO-8859-1 :EOL-STYLE :LF) #x30004276AF3D> #<FLEXI-STREAMS:FLEXI-IO-STREAM #x3000428BB9ED> "GET" 0 3) I'm running the following versions of things: drakma-1.0.0 flexi-streams-1.0.7 chunga-1.0.0 trivial-gray-streams-2008-11-02 UFFI 1.6.0 This appears at a cursory glance to be a bad interaction between flexi- streams and CCL's built-in unicode support. The EXTERNAL-FORMAT class is built in to CCL. It is not a flexi-streams class (nor a Chunga class). I would debug this myself but I got a report that someone is successfully running Drakma on CCL so I thought someone might just know the answer. Thanks, rg

2 3

[flexi-streams-devel] Signaling Condition on BOUND Invalidation
by Volkan YAZICI 20 Jan '09

20 Jan '09

Hi, Here is a small patch that introduces signaling of a condition when BOUND of an input stream is trying to be exceeded. Would Edi approve such a functionality? Regards.

2 2

[flexi-streams-devel] output-stream-sequence-length
by Takehiko Abe 03 Nov '08

03 Nov '08

flexi-streams-1.0.7 The simple-array type declaration in output-stream-sequence-length is wrong because the vector has fill-pointer and adjustable. (defmethod output-stream-sequence-length ((stream in-memory-output-stream)) (declare (optimize speed)) (with-accessors ((vector vector-stream-vector)) stream (length (the (simple-array * (*)) vector)))) regards, T.

1 0

Re: [flexi-streams-devel] Formatted output under CLISP
by Anton Vodonosov 15 Oct '08

15 Oct '08

on Thursday, October 16, 2008, 1:38:12 AM Mike wrote: > Thanks! This is a definite improvement. (and amazingly fast :-) > The patch seems to have changed the error message to where it's now > complaining about a slightly different generic function, this time > called on the underlying SWANK output stream: > NO-APPLICABLE-METHOD: When calling #1=#<STANDARD-GENERIC-FUNCTION > STREAM-WRITE-CHAR-SEQUENCE> with arguments #2=(#(72 101 108 > 108 111 32 87 111 114 108 ...) > #<SWANK-BACKEND::SLIME-OUTPUT-STREAM #x19F5DF19> 0 12), no method > is applicable. > [Condition of type METHOD-CALL-ERROR] > Is it reasonable to belive I need to provide a definition of the > method for the SLIME-OUTPUT-STREAM? Flexi-streams are designed to wrap binary stream - a stream that supports WRITE-BYTE and WRITE-SEQUENCE with a byte array as argument. SILE-OUTPUT-STREAM is a character stream, it inherits from FUNDAMENTAL-CHARACTER-OUTPUT-STREAM. Therefore, your example: (setq my-flexi-stream (flexi-streams:make-flexi-stream *standard-output*)) (format my-flexi-stream "Hello World!") is not 100% correct. As far as I understood, the example is only created to isolate the error you encountered when used Drakma with CLISP, and there is no real need to wrap *standard-output* by flexi-stream. With patched trivial-gray-streams Drakma must work in CLISP. Best regards, - Anton

1 0

[flexi-streams-devel] Formatted output under CLISP
by Mike Schaeffer 15 Oct '08

15 Oct '08

All, I'm currently trying to use DRAKMA on CLISP to write a script that will automatically fetch a web page and scrape some information out of a table. While trying to get this to work, I ran into an issue that I'm able to reproduce with only FLEXI-STREAMS. Given a fresh CLISP (with flexi-streams loaded via ASDF) I'm getting the following behavior: CL-USER> (format *standard-output* "Hello World!") Hello World!NIL CL-USER> (setq my-flexi-stream (flexi-streams:make-flexi-stream *standard-output*)) #<FLEXI-STREAMS:FLEXI-OUTPUT-STREAM #x1A0285F9> CL-USER> (format my-flexi-stream "Hello World!") At this point, I get the following error: NO-APPLICABLE-METHOD: When calling #1=#<STANDARD-GENERIC-FUNCTION STREAM-WRITE-BYTE-SEQUENCE> with arguments #2=(#(72 101 108 108 111 32 87 111 114 108 ...) #<FLEXI-STREAMS:FLEXI-OUTPUT-STREAM #x1A00D595> NIL 12), no method is applicable. [Condition of type METHOD-CALL-ERROR] The original error I encountered in Drakma is also easy to reproduce. I get the following error on the first call to DRAKMA:HTTP-REQUEST: NO-APPLICABLE-METHOD: When calling #1=#<STANDARD-GENERIC-FUNCTION STREAM-WRITE-BYTE-SEQUENCE> with arguments #2=(#(71 69 84) #<FLEXI-STREAMS:FLEXI-IO-STREAM #x1A0F01E5> NIL 3), no method is applicable. [Condition of type METHOD-CALL-ERROR] The #(71 69 84) is basically "GET", so this looks like the first write to the stream for the outgoing HTTP request. I'm still ascending the learning curve, so I'm not quite sure what to make of these errors, but my best guess is that maybe I have an inconsistent set of packages installed. Has anybody seen anything like this before? Google seems to think not. I've attached the output from the ASDF call (stripped of some directory names) at the end of this mail, if it's useful. Other possibly relevant information is that this is CLISP 2.45 (2008-05-15) and it's running on a Windows XP SP3 machine. Any help would be very much appreciated. Thanks, Mike ; loading system definition from ...\lisp\flexi-streams-1.0.7\flexi-streams.asd into #<PACKAGE ASDF0> ;; Loading file ...\lisp\flexi-streams-1.0.7\flexi-streams.asd ... ; registering #<SYSTEM :FLEXI-STREAMS #x19FA77A1> as FLEXI-STREAMS ; registering #<SYSTEM :FLEXI-STREAMS-TEST #x19F74771> as FLEXI-STREAMS-TEST ;; Loaded file ...\lisp\flexi-streams-1.0.7\flexi-streams.asd ; loading system definition from ...\lisp\trivial-gray-streams-2006-09-16\trivial-gray-streams.asd into #<PACKAGE ASDF0> ;; Loading file ...\lisp\trivial-gray-streams-2006-09-16\trivial-gray-streams.asd ... ; registering #<SYSTEM :TRIVIAL-GRAY-STREAMS #x19FD06A9> as TRIVIAL-GRAY-STREAMS ;; Loaded file ...\lisp\trivial-gray-streams-2006-09-16\trivial-gray-streams.asd ;; Loading file ...\lisp\trivial-gray-streams-2006-09-16\package.fas ... ;; Loaded file ...\lisp\trivial-gray-streams-2006-09-16\package.fas ;; Loading file ...\lisp\trivial-gray-streams-2006-09-16\mixin.fas ... WARNING: The generic function #<STANDARD-GENERIC-FUNCTION GRAY:STREAM-WRITE-CHAR-SEQUENCE> is being modified, but has already been called. ;; Loaded file ...\lisp\trivial-gray-streams-2006-09-16\mixin.fas ;; Loading file ...\lisp\flexi-streams-1.0.7\packages.fas ... ;; Loaded file ...\lisp\flexi-streams-1.0.7\packages.fas ;; Loading file ...\lisp\flexi-streams-1.0.7\mapping.fas ... ;; Loaded file ...\lisp\flexi-streams-1.0.7\mapping.fas ;; Loading file ...\lisp\flexi-streams-1.0.7\ascii.fas ... ;; Loaded file ...\lisp\flexi-streams-1.0.7\ascii.fas ;; Loading file ...\lisp\flexi-streams-1.0.7\koi8-r.fas ... ;; Loaded file ...\lisp\flexi-streams-1.0.7\koi8-r.fas ;; Loading file ...\lisp\flexi-streams-1.0.7\iso-8859.fas ... ;; Loaded file ...\lisp\flexi-streams-1.0.7\iso-8859.fas ;; Loading file ...\lisp\flexi-streams-1.0.7\code-pages.fas ... ;; Loaded file ...\lisp\flexi-streams-1.0.7\code-pages.fas ;; Loading file ...\lisp\flexi-streams-1.0.7\specials.fas ... ;; Loaded file ...\lisp\flexi-streams-1.0.7\specials.fas ;; Loading file ...\lisp\flexi-streams-1.0.7\util.fas ... ;; Loaded file ...\lisp\flexi-streams-1.0.7\util.fas ;; Loading file ...\lisp\flexi-streams-1.0.7\conditions.fas ... ;; Loaded file ...\lisp\flexi-streams-1.0.7\conditions.fas ;; Loading file ...\lisp\flexi-streams-1.0.7\external-format.fas ... ;; Loaded file ...\lisp\flexi-streams-1.0.7\external-format.fas ;; Loading file ...\lisp\flexi-streams-1.0.7\length.fas ... ;; Loaded file ...\lisp\flexi-streams-1.0.7\length.fas ;; Loading file ...\lisp\flexi-streams-1.0.7\encode.fas ... ;; Loaded file ...\lisp\flexi-streams-1.0.7\encode.fas ;; Loading file ...\lisp\flexi-streams-1.0.7\decode.fas ... ;; Loaded file ...\lisp\flexi-streams-1.0.7\decode.fas ;; Loading file ...\lisp\flexi-streams-1.0.7\in-memory.fas ... WARNING: The generic function #<STANDARD-GENERIC-FUNCTION STREAM-ELEMENT-TYPE> is being modified, but has already been called. ;; Loaded file ...\lisp\flexi-streams-1.0.7\in-memory.fas ;; Loading file ...\lisp\flexi-streams-1.0.7\stream.fas ... WARNING: The generic function #<STANDARD-GENERIC-FUNCTION CLOSE> is being modified, but has already been called. ;; Loaded file ...\lisp\flexi-streams-1.0.7\stream.fas ;; Loading file ...\lisp\flexi-streams-1.0.7\output.fas ... WARNING: The generic function #<STANDARD-GENERIC-FUNCTION STREAM-WRITE-CHAR> is being modified, but has already been called. WARNING: The generic function #<STANDARD-GENERIC-FUNCTION STREAM-FINISH-OUTPUT> is being modified, but has already been called. WARNING: The generic function #<STANDARD-GENERIC-FUNCTION STREAM-FORCE-OUTPUT> is being modified, but has already been called. WARNING: The generic function #<STANDARD-GENERIC-FUNCTION STREAM-LINE-COLUMN> is being modified, but has already been called. ;; Loaded file ...\lisp\flexi-streams-1.0.7\output.fas ;; Loading file ...\lisp\flexi-streams-1.0.7\input.fas ... WARNING: The generic function #<STANDARD-GENERIC-FUNCTION STREAM-CLEAR-INPUT> is being modified, but has already been called. ;; Loaded file ...\lisp\flexi-streams-1.0.7\input.fas ;; Loading file ...\lisp\flexi-streams-1.0.7\io.fas ... WARNING: The generic function #<STANDARD-GENERIC-FUNCTION STREAM-WRITE-CHAR> is being modified, but has already been called. ;; Loaded file ...\lisp\flexi-streams-1.0.7\io.fas ;; Loading file ...\lisp\flexi-streams-1.0.7\strings.fas ... ;; Loaded file ...\lisp\flexi-streams-1.0.7\strings.fas 0 errors, 0 warnings

2 1

[flexi-streams-devel] Error loading flexi-streams
by Watt Poosanguansit 29 Sep '08

29 Sep '08

Hi, I am loading some other libraries that requires flexi-streams and I ran into errors which I did not find anything on the web that can resolve it. I am running on CMUCL on Debian. I appreciate your help. Watt P. ; loading system definition from ; /usr/local/asdf-install/site-systems/flexi-streams.asd into ; #<The ASDF0 package> ;; Loading #P"/usr/local/asdf-install/site/flexi-streams-1.0.7/flexi-streams.asd". ; registering #<SYSTEM :FLEXI-STREAMS {5841F48D}> as FLEXI-STREAMS ; registering #<SYSTEM :FLEXI-STREAMS-TEST {58437BCD}> as FLEXI-STREAMS-TEST ; Compiling LAMBDA (.PV-CELL. .NEXT-METHOD-CALL. O C): ; Compiling Top-Level Form: ;; Loading #P"/var/cache/common-lisp-controller/1000/cmucl/local/usr/local/asdf-install/site/flexi-streams-1.0.7/packages.x86f". ;; Loading #P"/var/cache/common-lisp-controller/1000/cmucl/local/usr/local/asdf-install/site/flexi-streams-1.0.7/mapping.x86f". Error in function LISP::INTERNAL-LOAD: File has a fasl file type, but no fasl file header: "/var/cache/common-lisp-controller/1000/cmucl/local/usr/local/asdf-install/site/flexi-streams-1.0.7/ascii.x86f" [Condition of type SIMPLE-ERROR]

2 1

[flexi-streams-devel] New release 1.0.7
by Edi Weitz 26 Aug '08

26 Aug '08

ChangeLog: Version 1.0.7 2008-08-26 Don't read a second time if the first READ-SEQUENCE already reached EOF (Drakma bug report by Stas Boukarev) Download: http://weitz.de/files/flexi-streams.tar.gz Edi.

1 0