JehanneOS/mksh
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
mksh/tests
History
tg 5cb41399fe add a regression test which our current mksh does not pass, 
but the one fixed by a diff by jaredy@openbsd (which intro-
duces other problems though):
Log message:
Change the behavior of IFS word-splitting:  split words
when the current character is IFS space and the last
character was a word character or it was non-white IFS
space and the current character is non-white IFS space.
This deviates from the previous behavior because the
latter splits words when the last character is any IFS
space and the current is non-white IFS, resulting in
more fields most of the time.

This new behavior follows what the man page describes;
i.e., that a field is delimited by one or more IFS
whitespace characters followed by zero or one non-white
IFS characters.
2004-11-26 15:30:15 +00:00
..
alias.t
polish, mop up whitespace, etc.
2004-05-24 19:56:25 +00:00
arith.t
polish, mop up whitespace, etc.
2004-05-24 19:56:25 +00:00
bksl-nl.t
whitespace fix in comment
2004-11-01 12:27:22 +00:00
brkcont.t
polish, mop up whitespace, etc.
2004-05-24 19:56:25 +00:00
cdhist.t
Import OpenBSD 3.3 source repository from CTM 3132 the first time
2003-03-22 17:35:03 +00:00
eglob.t
polish, mop up whitespace, etc.
2004-05-24 19:56:25 +00:00
glob.t
polish, mop up whitespace, etc.
2004-05-24 19:56:25 +00:00
heredoc.t
polish, mop up whitespace, etc.
2004-05-24 19:56:25 +00:00
history.t
polish, mop up whitespace, etc.
2004-05-24 19:56:25 +00:00
ifs.t
add a regression test which our current mksh does not pass,
2004-11-26 15:30:15 +00:00
integer.t
polish, mop up whitespace, etc.
2004-05-24 19:56:25 +00:00
lineno.t
polish, mop up whitespace, etc.
2004-05-24 19:56:25 +00:00
read.t
polish, mop up whitespace, etc.
2004-05-24 19:56:25 +00:00
README
polish, mop up whitespace, etc.
2004-05-24 19:56:25 +00:00
regress.t
polish, mop up whitespace, etc.
2004-05-24 19:56:25 +00:00
syntax.t
polish, mop up whitespace, etc.
2004-05-24 19:56:25 +00:00
th
polish, mop up whitespace, etc.
2004-05-24 19:56:25 +00:00
th.sh
polish, mop up whitespace, etc.
2004-05-24 19:56:25 +00:00
unclass1.t
Import OpenBSD 3.3 source repository from CTM 3132 the first time
2003-03-22 17:35:03 +00:00
unclass2.t
polish, mop up whitespace, etc.
2004-05-24 19:56:25 +00:00
version.t
sync and bump to 1.16
2004-11-10 17:22:14 +00:00

README 

Tests can be assigned categories to restrict what program they
are applied to (eg, pdksh, ksh88, etc.).  The following are
a list of names to be used for various shells (to keep things
consistent):

    sh		generic		any v7 bourne shell like thing
    sh-v	generic		any system V bourne shell like thing
    ksh		generic		any ksh
    posix	generic		basic posix shell
    posix-upu	generic		'user portability utility' options
    sh-v7	specific	the real v7 bourne shell
    sh-sysv	specific	the real sysv bourne shell
    pdksh	specific	public domain ksh
    ksh88	specific	at&t ksh88
    ksh93	specific	at&t ksh93
    bash	specific	GNU bourne-again shell

The idea is to categorize all the tests according to the 'best match'
(most generic thing).  All generics that apply should be specified.
Generally, at most one specific shell will be given.

At the moment, most (all) tests have not been categorized (any volunteers?).