diff options
author | Jim Meyering <jim@meyering.net> | 2000-06-22 17:10:51 +0000 |
---|---|---|
committer | Jim Meyering <jim@meyering.net> | 2000-06-22 17:10:51 +0000 |
commit | 62e3f1f1ef36692e09330c58f86e81454cbdca02 (patch) | |
tree | f4c4fe3d999cc94ed9e10d34121122de0485d9e0 | |
parent | 1407c2894a5be4a0b815c04ba8f2809a075cbd6e (diff) | |
download | coreutils-62e3f1f1ef36692e09330c58f86e81454cbdca02.tar.xz |
(main): Correct a comment.
-rw-r--r-- | src/cat.c | 6 |
1 files changed, 3 insertions, 3 deletions
@@ -788,7 +788,7 @@ main (int argc, char **argv) { inbuf = (unsigned char *) xmalloc (insize + 1); - /* Why are (OUTSIZE - 1 + INSIZE * 4 + 13) bytes allocated for + /* Why are (OUTSIZE - 1 + INSIZE * 4 + 13) bytes allocated for the output buffer? A test whether output needs to be written is done when the input @@ -797,8 +797,8 @@ main (int argc, char **argv) buffer. Now INSIZE bytes of input is read. Each input character may grow by a factor of 4 (by the prepending of M-^). If all characters do, and no newlines appear in this block of input, we - will have at most (OUTSIZE - 1 + INSIZE) bytes in the buffer. If - the last character in the preceding block of input was a + will have at most (OUTSIZE - 1 + INSIZE * 4) bytes in the buffer. + If the last character in the preceding block of input was a newline, a line number may be written (according to the given options) as the first thing in the output buffer. (Done after the new input is read, but before processing of the input begins.) A |