Kevin Ryde <[EMAIL PROTECTED]> writes: > (I notice "write" style string output in iprin1() always goes > char-by-char, it'd be nice if it scanned ahead for a char needing an > escape, to send the non-escape block as a single lfwrite. Decent size > runs of plain chars are probably quite likely.)
I like this variant best. I don't think that writing strings with lots of escape sequences to an unbuffered port happens often enough to justify implementing a second buffering mechanism. When outputting an escaped char, we can additionally assemble the escape sequence in a fixed size buffer and then output that in one go. I will make that change myself in the next days, but if anyone beats me to it... -- GPG: D5D4E405 - 2F9B BCCC 8527 692A 04E3 331E FAF8 226A D5D4 E405 _______________________________________________ Guile-user mailing list Guile-user@gnu.org http://lists.gnu.org/mailman/listinfo/guile-user
