#586 WRITE-BYTE-SEQUENCE :no-hang t is only for byte vectors

lisp error
closed-fixed
Sam Steingold
clisp (525)
5
2011-04-06
2011-02-15
Don Cohen
No

[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

Discussion

  • Sam Steingold
    Sam Steingold
    2011-03-23

    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)

     
  • Sam Steingold
    Sam Steingold
    2011-03-23

    • milestone: --> lisp error
    • assigned_to: nobody --> haible
    • labels: --> clisp
     
  • Sam Steingold
    Sam Steingold
    2011-04-06

    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).

     
  • Sam Steingold
    Sam Steingold
    2011-04-06

    • assigned_to: haible --> sds
    • summary: WRITE-BYTE-SEQUENCE :no-hang t => error --> WRITE-BYTE-SEQUENCE :no-hang t is only for byte vectors
    • status: open --> closed-fixed