Add a FLAGS argument to AT_CHECK_M4SUGAR_TEXT.

This is not actually used within the testsuite at present, but is
handy for troubleshooting m4sugar tests.  For instance, you can pass
-v to a specific autom4te invocation and get told the underlying m4
invocation.

* tests/m4sugar.at (AT_CHECK_M4SUGAR_TEXT): Add fourth argument
  FLAGS which specifies additional command line arguments to pass to
  autom4te.

diff --git a/tests/m4sugar.at b/tests/m4sugar.at
index ba7191afc8a9453041d4f3c6ebe04c8413462bc2..7ea786b74cdf13705bad1cbab077f566e6e83e1c 100644 (file)
--- a/tests/m4sugar.at
+++ b/tests/m4sugar.at
@@ -19,8 +19,8 @@ AT_BANNER([M4sugar.])
 # along with this program.  If not, see <https://www.gnu.org/licenses/>.
 
 
-# AT_CHECK_M4SUGAR_TEXT(CODE, STDOUT, STDERR)
-# -------------------------------------------
+# AT_CHECK_M4SUGAR_TEXT(CODE, STDOUT, STDERR, FLAGS)
+# --------------------------------------------------
 # Check that m4sugar CODE expands to STDOUT and emits STDERR.
 m4_define([AT_CHECK_M4SUGAR_TEXT],
 [
@@ -31,7 +31,7 @@ m4_divert_push([])[]dnl
 m4_divert_pop([])
 ]])
 
-AT_CHECK_M4SUGAR([-o-],, [$2], [$3])
+AT_CHECK_M4SUGAR([$4 -o-],, [$2], [$3])
 ])# AT_CHECK_M4SUGAR_TEXT