From ee28883f0eb709933bad58b4b84575210c3fd939 Mon Sep 17 00:00:00 2001 From: Ralf Wildenhues Date: Mon, 26 Nov 2007 19:36:48 +0100 Subject: [PATCH] Document Tru64 awk input splitting limitation. * doc/autoconf.texi (Limitations of Usual Tools) : Document that Tru64 awk always splits $0. --- ChangeLog | 5 +++++ doc/autoconf.texi | 7 ++++--- 2 files changed, 9 insertions(+), 3 deletions(-) diff --git a/ChangeLog b/ChangeLog index 60a292d3..7d35a0bd 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,3 +1,8 @@ +2007-11-26 Ralf Wildenhues + + * doc/autoconf.texi (Limitations of Usual Tools) : + Document that Tru64 awk always splits $0. + 2007-11-24 Stepan Kasal * lib/autotest/general.m4 (AT_INIT): Do not extract the diff --git a/doc/autoconf.texi b/doc/autoconf.texi index 76d4b777..d6bd7866 100644 --- a/doc/autoconf.texi +++ b/doc/autoconf.texi @@ -14487,9 +14487,10 @@ In code portable to both traditional and modern Awk, @code{FS} must be a string containing just one ordinary character, and similarly for the field-separator argument to @code{split}. -Traditional Awk has a limit of 99 -fields in a record. You may be able to circumvent this problem by using -@code{split}. +Traditional Awk has a limit of 99 fields in a record. Since some Awk +implementations, like Tru64's, split the input even if you don't refer +to any field in the script, to circumvent this problem, set @samp{FS} +to an unusual character and use @code{split}. Traditional Awk has a limit of at most 99 bytes in a number formatted by @code{OFMT}; for example, @code{OFMT="%.300e"; print 0.1;} typically -- 2.47.2