From: SourceForge.net <no...@so...> - 2006-12-27 23:20:12
|
Bugs item #1483762, was opened at 2006-05-08 08:05 Message generated for change (Comment added) made by sds You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=101355&aid=1483762&group_id=1355 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: clisp Group: lisp error >Status: Closed >Resolution: Fixed Priority: 5 Private: No Submitted By: Jörg Höhle (hoehle) Assigned to: Sam Steingold (sds) Summary: socket's stream-external-format always :default Initial Comment: Due to the splitting of the <IO SOCKET-STREAM> into two individual sockets, STREAM-EXTERNAL-FORMAT behaves badly and constantly yields :DEFAULT. [1]> (socket-server 4556) #<SOCKET-SERVER 0.0.0.0:4556> [2]> (setq sr *) #<SOCKET-SERVER 0.0.0.0:4556> [3]> (setq s (socket-accept sr)) ; now telnet into server #<IO INPUT-BUFFERED SOCKET-STREAM CHARACTER 0.0.0.0:4556> [4]> (stream-external-format s) :DEFAULT [5]> (setf (stream-external-format s) charset:cp437) #<ENCODING CHARSET:CP437 :UNIX> [6]> (stream-external-format s) :DEFAULT The individual INPUT and OUTPUT only components report the right results. [7]> (sys::%record-ref s 14) #<INPUT BUFFERED SOCKET-STREAM CHARACTER 0.0.0.0:4556> [8]> (stream-external-format *) #<ENCODING CHARSET:CP437 :UNIX> [9]> (sys::%record-ref s 15) #<OUTPUT UNBUFFERED SOCKET-STREAM CHARACTER 0.0.0.0:4556> [10]> (stream-external-format *) #<ENCODING CHARSET:CP437 :UNIX> ---------------------------------------------------------------------- Comment By: Sam Steingold (sds) Date: 2006-12-27 18:20 Message: Logged In: YES user_id=5735 Originator: NO thank you for your bug report. the bug has been fixed in the CVS tree. you can either wait for the next release (recommended) or check out the current CVS tree (see http://clisp.cons.org) and build CLISP from the sources (be advised that between releases the CVS tree is very unstable and may not even build on your platform). ---------------------------------------------------------------------- Comment By: Sam Steingold (sds) Date: 2006-12-27 16:05 Message: Logged In: YES user_id=5735 Originator: NO this is the general property of composite streams: they return :default. what should they return if the composite streams have different external formats? http://www.lisp.org/HyperSpec/Body/fun_stream-external-format.html does not specify any exceptional situations, so, presumably, we cannot signal an error. return :default? note that for broadcast streams we only look at the last stream because of http://www.lisp.org/HyperSpec/Issues/iss021-writeup.html should we do full recursion for two-way streams? concatenated streams? &c &c it is not clear that the current CLISP behavior is actually broken. ---------------------------------------------------------------------- Comment By: Sam Steingold (sds) Date: 2006-12-27 16:05 Message: Logged In: YES user_id=5735 Originator: NO This bug report is now marked as "pending"/"invalid". This means that we think that the problem you report is not a problem with CLISP. Unless you - the reporter - act within 2 weeks, the bug will be permanently closed. Sorry about the inconvenience - we hope your silence means that you agree that this is not a bug in CLISP. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=101355&aid=1483762&group_id=1355 |