From 3b4b3ee585509f69d72df963e73665f07b95923c Mon Sep 17 00:00:00 2001 From: Paul Eggert Date: Thu, 5 Jan 2012 11:00:45 -0800 Subject: [PATCH] doc: clarify sed buffer limit * doc/autoconf.texi (Limitations of Usual Tools): That 4000-byte limit applies to output and internal buffers, too. --- ChangeLog | 6 ++++++ doc/autoconf.texi | 5 +++-- 2 files changed, 9 insertions(+), 2 deletions(-) diff --git a/ChangeLog b/ChangeLog index 30312bee..238c09f6 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,3 +1,9 @@ +2012-01-05 Paul Eggert + + doc: clarify sed buffer limit + * doc/autoconf.texi (Limitations of Usual Tools): + That 4000-byte limit applies to output and internal buffers, too. + 2012-01-03 Paul Eggert maint: update copyright year diff --git a/doc/autoconf.texi b/doc/autoconf.texi index 72ff7f89..ea2419bc 100644 --- a/doc/autoconf.texi +++ b/doc/autoconf.texi @@ -19256,8 +19256,9 @@ $ @kbd{echo a | sed 's/x/x/;;s/x/x/'} sed: 1: "s/x/x/;;s/x/x/": invalid command code ; @end example -Input should not have unreasonably long lines, since some @command{sed} -implementations have an input buffer limited to 4000 bytes. Likewise, +Some @command{sed} implementations have a buffer limited to 4000 bytes, +and this limits the size of input lines, output lines, and internal +buffers that can be processed portably. Likewise, not all @command{sed} implementations can handle embedded @code{NUL} or a missing trailing newline. -- 2.47.2