Re: string too long from write-char
[email protected] (Don Cohen)
| Newsgroups | gmane.lisp.clisp.general |
|---|---|
| Message-ID | <[email protected]> |
The point is that you write to iq::data, you say that it's bound to cl:*terminal-io*, but we have no reason to believe you. No, that's not what I said. Data is bound to a generic stream. However, by the time we get down to write_char we're writing to *terminal-io*. And I agree that simply writing spaces to *terminal-io* does not exhibit this problem - one of my first tests. So there's still a question of what's going on inside of write_char that is different for generic streams. I suppose I could continue to simplify the code that I've not yet sent you in order to generate a simple reproducible case, but I was hoping someone who was familiar with the write_char code would know more about why it calls ssstring_push_extend, and under what circumstance that happens. ------------------------------------------------------------------------------ _______________________________________________ clisp-list mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/clisp-list