minix/tests/lib/libc/regex/README
Lionel Sambuc 11be35a165 Importing NetBSD "Kyua" test framework
To do so, a few dependencies have been imported:

 * external/bsd/lutok
 * external/mit/lua
 * external/public-domain/sqlite
 * external/public-domain/xz

The Kyua framework is the new generation of ATF (Automated Test
Framework), it is composed of:

 * external/bsd/atf
 * external/bsd/kyua-atf-compat
 * external/bsd/kyua-cli
 * external/bsd/kyua-tester
 * tests

Kyua/ATF being written in C++, it depends on libstdc++ which is
provided by GCC. As this is not part of the sources, Kyua is only
compiled when the native GCC utils are installed.

To install Kyua do the following:

 * In a cross-build enviromnent, add the following to the build.sh
   commandline: -V MKBINUTILS=yes -V MKGCCCMDS=yes

WARNING:
  At this point the import is still experimental, and not supported
  on native builds (a.k.a make build).

Change-Id: I26aee23c5bbd2d64adcb7c1beb98fe0d479d7ada
2013-07-23 20:43:41 +02:00

33 lines
1.4 KiB
Text

regular expression test set
Lines are at least three fields, separated by one or more tabs. "" stands
for an empty field. First field is an RE. Second field is flags. If
C flag given, regcomp() is expected to fail, and the third field is the
error name (minus the leading REG_).
Otherwise it is expected to succeed, and the third field is the string to
try matching it against. If there is no fourth field, the match is
expected to fail. If there is a fourth field, it is the substring that
the RE is expected to match. If there is a fifth field, it is a comma-
separated list of what the subexpressions should match, with - indicating
no match for that one. In both the fourth and fifth fields, a (sub)field
starting with @ indicates that the (sub)expression is expected to match
a null string followed by the stuff after the @; this provides a way to
test where null strings match. The character `N' in REs and strings
is newline, `S' is space, `T' is tab, `Z' is NUL.
The full list of flags:
- placeholder, does nothing
b RE is a BRE, not an ERE
& try it as both an ERE and a BRE
C regcomp() error expected, third field is error name
i REG_ICASE
m ("mundane") REG_NOSPEC
s REG_NOSUB (not really testable)
n REG_NEWLINE
^ REG_NOTBOL
$ REG_NOTEOL
# REG_STARTEND (see below)
p REG_PEND
For REG_STARTEND, the start/end offsets are those of the substring
enclosed in ().