Re: typo in test cases

walter harms wrote: > hi chet, > > #! > may have unexpected side effects. e.g. i got 'unknown interpreter' while > locating a problem. Such side effects indicate a problem with the test environment. That script, and nearly all of the `.sub' scripts in the bash test directory, is supposed to be r

Re: typo in test cases

hi chet, #! may have unexpected side effects. e.g. i got 'unknown interpreter' while locating a problem. re, wh Chet Ramey wrote: > walter harms wrote: >> hi bash-developer, >> i used the bash test suite to check busybox ash and found >> two possible mistakes in the latest release. > [...

Re: typo in test cases

walter harms wrote: > hi bash-developer, > i used the bash test suite to check busybox ash and found > two possible mistakes in the latest release. [...] > > 1. func.tests:FUCNAME=7 >possible typo: FUNCNAME ? Thanks, this is indeed a typo. > > 2. getopts5.sub: hardcoded interpreter

typo in test cases

hi bash-developer, i used the bash test suite to check busybox ash and found two possible mistakes in the latest release. since the fix is trivial i did not add a patch. please add a comment to the source if they are intended. re, walter 1. func.tests:FUCNAME=7 possible typo: FUNCNAME ? 2.