If I remember correctly, some assertion numbers are a little bit off
because the test suite was written based on a late draft of the standard
rather than on the final 2003.2 standard and some (but very few)
assertions were renumbered before the final standard was published. In
this case, it looks like they match.
Note also that 2003.2 wasn't updated when 1003.2 and 1003.1 revisions
were approved. I believe the test suite writer added assertion based
on changes to the underlying standard, so 2003.2-1996 may not list all
of the assertions being tested by VSC.
>
> what is content of the "isn't empty" standard error? a newline? a space?
Since I no longer work for Sun/Oracle, I don't have access to the log file.
>
> is it at all possible to provide a command sequence of what its complaining
> about?
> or would "echo foo &" be enough to violate the VSC pact?
Since I'm no longer employed by a company with a VSC license, I'm afraid
I can't help with the above two questions. ;-{
Hoping it will help, the full assertion text for the other failures listed
in Bug ID 6901715 are:
028(C) If the User Portability Utilities Option is supported:
When the POSIX locale is specified and a background job is
suspended by a SIGTTIN signal then the <state> field in the output
message is set to Stopped(SIGTTIN) or Suspended(SIGTTIN).
029(C) If the User Portability Utilities Option is supported:
When the POSIX locale is specified and a background job is
suspended by a SIGTTOU signal then the <state> field in the output
message is set to Stopped(SIGTTOU) or Suspended(SIGTTOU).
Assertions 81 and later don't match, they could be based on:
81(C)???
091(C) If the User Portability Utilities Option is supported and shell
command
line editing is supported:
When in insert mode an entered character other than <newline>,
erase, interrupt, kill, control-V, control-W, backslash \ (followed
by
erase or kill),
83(C)???
093(C) If the User Portability Utilities Option is supported and shell
command
line editing is supported:
After termination of a previous command, sh is entered in insert
mode.
84(C)
094(C) If the User Portability Utilities Option is supported and shell
command
line editing is supported:
When in insert mode an <ESC> switches sh into command mode.
86(C)
096(C) If the User Portability Utilities Option is supported and shell
command
line editing is supported:
When in command mode the interrupt character causes sh to terminate
command line editing on the current command line, re-issue
the prompt on the next line of the terminal and to reset the command
history so that the command that was interrupted is not
entered in the history.
87(C)
097(C) If the User Portability Utilities Option is supported and shell
command
line editing is supported:
When in insert mode a <newline> causes the current command
line to be executed.
89(C)
099(C) If the User Portability Utilities Option is supported and shell
command
line editing is supported:
When in insert mode the interrupt character causes sh to terminate
command line editing on the current command line, re-issue the
prompt on the next line of the terminal and to reset the command
history so that the command that was interrupted is not entered in
the history.
90(C)
100(C) If the User Portability Utilities Option is supported and shell
command
line editing is supported:
When in insert mode the kill character clears all the characters
from the input line.
91(C)
101(C) If the User Portability Utilities Option is supported and shell
command
line editing is supported:
When in insert mode a control-V causes the next character to be
inserted even in the case that the character is a special insert mode
character.
Testing Requirements:
The assertion must be tested with at least the following set of
characters: <newline>, erase, interrupt, kill, control-V, control-W,
end-of-file, backslash \ (followed by erase or kill) and <ESC>.
94(C)
104(C) If the User Portability Utilities Option is supported and shell
command
line editing is supported:
When in insert mode an end-of-file at the beginning of an input line
is interpreted as the end of input.
101(C)
111(C) If the User Portability Utilities Option is supported and shell
command
line editing is supported:
When in command mode, # inserts the character # at the beginning
of the command line and causes the line to be treated as a comment
and the line is entered in the command history.
127(C)
137(C) If the User Portability Utilities Option is supported and shell
command
line editing is supported:
When in command mode, then v invokes the vi editor to edit the
current command line in a temporary file. When the editor exits,
the commands in the temporary file are executed.
242(C)
251(C) If the User Portability Utilities Option is supported and shell
command
line editing is supported:
When in command mode, then the command N repeats the most
recent / or ? command, reversing the direction of the search.
Hope this helps,
Don
>
> -- Glenn Fowler -- at&t Research, Florham Park NJ --
