Re: Linefeed character in SBCL

On Mar 30, 11:06 am, dstein64 <DStei...@xxxxxxxxx> wrote:
I tried searching the SBCL manual but couldn't find anything. It seems
that the #\Linefeed character is synonymous with the #\Newline
character in SBCL. I feel this way because (write-char #\Linefeed
stream) returns #\Newline.

How can I access the distinct Linefeed character in SBCL? Thanks.

Actually, I believe it makes no difference for what I'm doing. This
post can be ignored.
.

Relevant Pages

  • Re: getting a simple-base-string from read-line
    ... > I've been doing some reading from files in SBCL and I was hoping I could ... > (SIMPLE-ARRAY CHARACTER (3)) CHARACTER ... > lines to be of type simple-base-string in SBCL and SBCL compained loudly ... The reason for this flexibility is to allow implementations to choose ...
    (comp.lang.lisp)
  • Re: Speed: a column of floats from large file
    ... Well, no, because as you said the bottleneck for SBCL is in READ-LINE, ... for external formats on character streams: ... asked for (whether explicitly through an:external-format argument, ... the bottleneck is likely to be in parsing the float. ...
    (comp.lang.lisp)
  • Re: Changing stream :element-type
    ... >> Note that the LANG=C hack to write octets to a character stream appears to ... The POSIX C locale, in character set terms, corresponds pretty closely ... such, using it to encode octets is a pretty poor idea, because, as ... been written by sbcl users and developers of the simple-streams ...
    (comp.lang.lisp)
  • Re: Speed: a column of floats from large file
    ... in SBCL these days there is quite aggressively pessimized support ... > for external formats on character streams: ... > asked for (whether explicitly through an:external-format argument, ...
    (comp.lang.lisp)
  • Re: Linefeed character in SBCL
    ... character in SBCL. ... How can I access the distinct Linefeed character in SBCL? ... WRITE-CHAR returns that because that's what it was given, ... been the ASCII coding is something I never really noticed until just ...
    (comp.lang.lisp)