summaryrefslogtreecommitdiff
path: root/testsuite/sed/sed-append-next-line
diff options
context:
space:
mode:
authorRob Landley2005-11-10 06:26:40 +0000
committerRob Landley2005-11-10 06:26:40 +0000
commit990025a7d971bbbdd982d2d070d3e47628d0fac0 (patch)
tree21e56ca95118f3874f7a889c285921377df47552 /testsuite/sed/sed-append-next-line
parentecfd1f6a350c91bd2b562cd3d04c160a54debc61 (diff)
downloadbusybox-990025a7d971bbbdd982d2d070d3e47628d0fac0.zip
busybox-990025a7d971bbbdd982d2d070d3e47628d0fac0.tar.gz
Ok, I've converted the contents of the "testing/sed" directory into a
sed.tests file. My brain hurts now. (Lots of boggling at sed minutiae and corner cases and going "why is gnu giving that output". The behavior of N and n with regard to EOF are only understandable if you read the Open Group spec, not if you read the sed info page, by the way...) Some of the existing sed tests are just nuts. For example, sed-next-line is testing for our behavior (which is wrong), and would fail if run against gnu sed (which was getting it right. Again, this was a spec-boggling moment, with much head scratching. I've got to add a debug mode where the stuff output by the p command is a different color from the stuff output by normal end of script printing (when not suppressed by -n).) As for sed-handles-unsatisifed-backrefs: what is this test trying to _do_? I ran it against gnu sed and got an error message, and this behavior sounds perfectly reasonable. (It _is_ an unsatisfied backref.) The fact we currently ignore this case (and treat \1 as an empty string) isn't really behavior we should have a test depend on for success. The remaining one is sed-aic-commands, which is long and complicated. I'm trying to figure out if I should chop this into a number of smaller tests, or if having one big "does-many-things" test is a good idea. In any case, the _next_ step is to go through the Open Group standard and make tests for every case not yet covered. (And there are plenty. There are few comments in the file already.) Plus I have notes about corner cases from development that I need to collate and put into here. This file is maybe the first 1/3 of a truly comprehensive sed test. Rob
Diffstat (limited to 'testsuite/sed/sed-append-next-line')
-rw-r--r--testsuite/sed/sed-append-next-line19
1 files changed, 0 insertions, 19 deletions
diff --git a/testsuite/sed/sed-append-next-line b/testsuite/sed/sed-append-next-line
deleted file mode 100644
index 0621a31..0000000
--- a/testsuite/sed/sed-append-next-line
+++ /dev/null
@@ -1,19 +0,0 @@
-# This will fail if CONFIG_FEATURE_SED_GNU_COMPATABILITY is defined
-busybox sed 'N;p'>output <<EOF
-a
-b
-c
-EOF
-
-set +e
-cmp -s output - <<EOF
-a
-b
-a
-b
-c
-EOF
-if [ $? != 0 ] ; then
- exit 0;
-fi
-exit 1;