Bugs item #3182597, was opened at 2011-02-15 13:19
Message generated for change (Comment added) made by sds
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=101355&aid=3182597&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: Don Cohen (donc)
>Assigned to: Sam Steingold (sds)
>Summary: WRITE-BYTE-SEQUENCE :no-hang t is only for byte vectors
Initial Comment:
[3]> (EXT:WRITE-BYTE-SEQUENCE #(1) f :no-hang t)
*** - WRITE-BYTE-SEQUENCE on
#<OUTPUT BUFFERED FILE-STREAM (UNSIGNED-BYTE 8) #P"/tmp/out1"> is illegal
works when array is element-type (unsigned-byte 8)
(the bug is that it does not work for other types)
same problem for unbuffered streams
----------------------------------------------------------------------
Comment By: Sam Steingold (sds)
Date: 2011-04-06 13:02
Message:
thank you for your bug report.
the bug has been fixed in the source tree (mercurial/hg).
you can either wait for the next release (recommended)
or check out the current mercurial tree (see http://clisp.org)
and build CLISP from the sources (be advised that between
releases the source tree is very unstable and may not even build
on your platform).
----------------------------------------------------------------------
Comment By: Sam Steingold (sds)
Date: 2011-03-23 17:17
Message:
this comes from
if (no_hang || interactive) /* FIXME: need write_byte_will_hang_p()
*/
error_illegal_streamop(S(write_byte_sequence),STACK_3);
in sequence.d (and similar comment in stream.d).
PTC.
workaround: use binary arrays (as you have noticed yourself)
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=101355&aid=3182597&group_id=1355
|
