From ff3a5ecf6f6bf9bb87682272f3eb800329572833 Mon Sep 17 00:00:00 2001 From: Laurent Bercot Date: Mon, 28 Apr 2025 08:43:53 +0000 Subject: Latest batch of fixes Signed-off-by: Laurent Bercot --- doc/eltest.html | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) (limited to 'doc/eltest.html') diff --git a/doc/eltest.html b/doc/eltest.html index f2d5bf5..208b0ab 100644 --- a/doc/eltest.html +++ b/doc/eltest.html @@ -31,13 +31,13 @@ exit status.

eltest acts as the generic POSIX -test utility, +test utility, but it diverges from the specification on how it parses ambiguous arguments: see below.

eltest supports all the standard -test +test operands, plus all the extensions from GNU test, plus a few extensions from the test builtin from @@ -64,7 +64,7 @@ valid, always returns the result of the expression no matter how complex it is.

eltest is not suitable as a Single Unix -test +test program, due to the way it disambiguates between arguments and operators, see below. However, if you never use arguments that start with a backslash, or that have the same name as an existing operator, then @@ -108,7 +108,7 @@ in order to match whole strings, you must anchor pattern with

Argument disambiguation

- Unlike test, + Unlike test, which has different fixed syntax trees depending on the number of arguments it receives and has undefined behaviour when called with more than 5 arguments, eltest accepts any number of arguments and builds its syntax trees on the fly. This means that expressions such @@ -122,7 +122,7 @@ when it reads the second -n it exits with a syntax error. Doing otherwise would result in a combinatory explosion of possible syntax trees, making it easy for users to trigger unbounded RAM consumption, and turning a simple utility into a programming nightmare. This is why POSIX -test +test is so restricted. But we don't want the same restrictions.

-- cgit v1.3.1