Xref: utzoo comp.lang.c:10521 comp.lang.c++:1210 Path: utzoo!attcan!uunet!husc6!uwvax!rutgers!rochester!cornell!uw-beaver!teknowledge-vaxc!sri-unix!quintus!ok From: ok@quintus.UUCP (Richard A. O'Keefe) Newsgroups: comp.lang.c,comp.lang.c++ Subject: Re: I/O implementation in C and C++ Keywords: C++, I/O, buffer allocation Message-ID: <1046@cresswell.quintus.UUCP> Date: 1 Jun 88 08:12:31 GMT References: <462@polari.UUCP> Organization: Quintus Computer Systems, Mountain View, CA Lines: 12 In article <462@polari.UUCP>, rlb@polari.UUCP (rlb) writes: > I find it interesting that both K&R (C) and Stroustrup (C++) give > I/O package implementation examples in which buffer allocation takes > place at the first I/O, rather than in the "open". [lines deleted] > Are there other advantages? The point is, I believe, to allow you to assign your own buffer. The sequence is fopen() setbuf() | setbuffer() | setvbuf() {IO}