>There is no precise definition of "acceptable"
Yes currently there isn't , but it would be easy to make such a definition,
simply, for various failure errno numbers (which are enumerated in the
standard), say "acceptable", "not acceptable", or perhaps "unspecified".
There is no precise definition of "acceptable", effectively. It's tied
into the requirements specific processors
or platforms have on where code and data can be placed in memory, which is
outside C's and POSIX's
scope. Most systems elect to localize all the (gory) details of creating
an
Mark Galeck wrote:
> Hello,
> the shell standard section on Command Search and Execution, says
> command shall be searched for using the PATH environment variable as
> described in XBD Environment Variables
> and that section says the value of PATH is split into a
Yes, thank you, alternative 3, I was wrong.
On 11/21/16 11:32 PM, Mark Galeck wrote:
> "The list shall be searched from beginning to end, applying the filename to
> each prefix, until an executable file with the specified name and
> appropriate execution permissions is found".
>
> Well, that is not how both dash and bash behave. They do
Hello,
the shell standard section on Command Search and Execution, says
command shall be searched for using the PATH environment variable as described
in XBD Environment Variables
and that section says the value of PATH is split into a list and
"The list shall be searched from beginning to