Path: utzoo!utgpu!news-server.csri.toronto.edu!clyde.concordia.ca!uunet!cs.utexas.edu!usc!snorkelwacker!ira.uka.de!smurf!urlichs From: urlichs@smurf.sub.org (Matthias Urlichs) Newsgroups: comp.lang.perl Subject: Re: (f)flush? Message-ID: Date: 5 Aug 90 16:27:40 GMT References: <1990Aug2.225410.2587@NCoast.ORG> <8992@jpl-devvax.JPL.NASA.GOV> <1990Aug4.191307.10807@NCoast.ORG> Organization: University of Karlsruhe, FRG Lines: 28 In comp.lang.perl, article <1990Aug4.191307.10807@NCoast.ORG>, allbery@ncoast.ORG (Brandon S. Allbery KB8JRR/KT) writes: < < But stdio buffers at something between 512 bytes and 8K by default, depending < on the implementation. On the machines I use, it's 1K; that's a far cry from < 512K blocks on a tape drive.... < Why don't we just make $| be the stdio buffer size of the current file handle? Zero is the default stdio buffer, a buffer size of one obviously says "unbuffered", and anything else setvbuf()s a buffer of that size. Or does anyone set $| to anything other than 0 and 1 in their scripts? Larry Wall writes: < +--------------- < | On machines with syscall(), you can get around dumb stdio limitations using < | it. It might be worthwhile for me to add a sysread() and syswrite() < | builtin to bypass stdio. < +--------------- Better to create a "real" perl interface for it. (The other system call which I can't do right now is called "alarm", BTW.) -- Matthias Urlichs -- urlichs@smurf.sub.org -- urlichs@smurf.ira.uka.de Humboldtstrasse 7 - 7500 Karlsruhe 1 - FRG -- +49+721+621127(Voice)/621227(PEP)