Test syntax documentation in B01cd is wrong?

Test syntax documentation in B01cd is wrong?

[Bart Schaefer]

The comment says:

# The first line (only) of a '>' and '?' chunk may be preceded by a '*',
# so the line starts '*>' or '*?'.  This signifies that all lines in the
# chunk (not just the one with the '*' in front) in the actual output
# are pattern matched against the corresponding lines in the test
# output.

But in fact it appears you have to start EVERY line that needs to be
pattern matched with "*>" or "*?" -- see, for example, in A02alias:

0:Aliasing reserved tokens
>begin
>end
*>*5*{ begin
*>*6*{end

Not only is that not *> on the first line, but there are two lines with
the leading splat.  Similarly in B06fc.

Re: Test syntax documentation in B01cd is wrong?

[Peter Stephenson]

On Sun, 22 Nov 2015 14:05:33 -0800
Bart Schaefer <schaefer@brasslantern.com> wrote:
> The comment says:
> 
> # The first line (only) of a '>' and '?' chunk may be preceded by a '*',
> # so the line starts '*>' or '*?'.  This signifies that all lines in the
> # chunk (not just the one with the '*' in front) in the actual output
> # are pattern matched against the corresponding lines in the test
> # output.
> 
> But in fact it appears you have to start EVERY line that needs to be
> pattern matched with "*>" or "*?" -- see, for example, in A02alias:

Looks to me from the test driver that it should work on *any* line, not
just the first.

pws

Re: Test syntax documentation in B01cd is wrong?

[Bart Schaefer]

On Nov 23,  3:26pm, Peter Stephenson wrote:
} Subject: Re: Test syntax documentation in B01cd is wrong?
}
} Looks to me from the test driver that it should work on *any* line, not
} just the first.

diff --git a/Test/B01cd.ztst b/Test/B01cd.ztst
index a5b3769..94447e7 100644
--- a/Test/B01cd.ztst
+++ b/Test/B01cd.ztst
@@ -57,13 +57,13 @@
 # subsequent whitespace being significant; lines are not subject to any
 # substitution unless the `q' flag (see below) is set.
 #
-# The first line (only) of a '>' and '?' chunk may be preceded by a '*',
-# so the line starts '*>' or '*?'.  This signifies that all lines in the
-# chunk (not just the one with the '*' in front) in the actual output
-# are pattern matched against the corresponding lines in the test
-# output.  Each line following '>' or '?' must be a valid pattern, so
-# characters special to patterns such as parentheses must be quoted
-# with a backslash.  The EXTENDED_GLOB option is used for all such patterns.
+# Each line of a '>' and '?' chunk may be preceded by a '*', so the line
+# starts '*>' or '*?'.  This signifies that for any line with '*' in front
+# the actual output should be pattern matched against the corresponding
+# lines in the test output.  Each line following '>' or '?' must be a
+# valid pattern, so characters special to patterns such as parentheses
+# must be quoted with a backslash.  The EXTENDED_GLOB option is used for
+# all such patterns.
 #
 # Each chunk of indented code is to be evaluated in one go and is to
 # be followed by a line starting (in the first column) with

-- 
Barton E. Schaefer