From c30a8963a2778ce4e1bd73b5fa667a2fff3693f2 Mon Sep 17 00:00:00 2001 From: Robin Haberkorn Date: Sat, 29 Mar 2025 16:53:34 +0300 Subject: bumped target release to v2.4.0 and updated README and TODO * Added a test case for the known bug of out-of-place modifiers. Well, this is a syntactic shortcoming rather than a true bug. But I did run into it more than once. --- tests/testsuite.at | 8 ++++++++ 1 file changed, 8 insertions(+) (limited to 'tests/testsuite.at') diff --git a/tests/testsuite.at b/tests/testsuite.at index c1256c7..cb1fe61 100644 --- a/tests/testsuite.at +++ b/tests/testsuite.at @@ -333,11 +333,19 @@ AT_XFAIL_IF(true) AT_CLEANUP AT_SETUP([Dangling Else/End-If]) +# Should throw syntax errors. AT_CHECK([$SCITECO -e "'"], 1, ignore, ignore) AT_CHECK([$SCITECO -e "| (0/0) '"], 1, ignore, ignore) AT_XFAIL_IF(true) AT_CLEANUP +AT_SETUP([Out-of-place modifiers]) +# NOTE: `J` does not currently support @-modifiers. +# This should be a syntax error. +AT_CHECK([$SCITECO -e "@I/foo^J/ @J Xa"], 1, ignore, ignore) +AT_XFAIL_IF(true) +AT_CLEANUP + # NOTE: This bug depends on specific build options of Glib's # PCRE which is not predictable. # It segfaults at least on Ubuntu 20.04 (libpcre3 v2:8.39). -- cgit v1.2.3