* Sascha Ziemann <cev...@gmail.com> [110921 10:11]: > What the hell does write-line do? > > I used this script: > > #! /usr/local/bin/csi -s > > (define (write-line* line) > (display line) > (newline)) > > (if (not (null? (command-line-arguments))) > (set! write-line write-line*)) > > (let next-line ((line (read-line))) > (if (not (eof-object? line)) > (begin > (write-line line) > (next-line (read-line))))) > > The build in write-line: > > $ dd if=/dev/zero bs=1M count=100 | od -xv | cat.scm > /dev/null > 100+0 records in > 100+0 records out > 104857600 bytes (105 MB) copied, 18.7047 s, 5.6 MB/s > > The self written version: > > $ dd if=/dev/zero bs=1M count=100 | od -xv | cat.scm 1 > /dev/null > 100+0 records in > 100+0 records out > 104857600 bytes (105 MB) copied, 13.3583 s, 7.8 MB/s
Did you also switch off line buffering on the port? Maybe that's what's holding you up there for some reason? Just a guess though... -- Who can (make) the muddy water (clear)? Let it be still, and it will gradually become clear. Who can secure the condition of rest? Let movement go on, and the condition of rest will gradually arise. -- Lao Tse. _______________________________________________ Chicken-users mailing list Chicken-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/chicken-users
