Implementation of the rule SH.FLOW.CheckCodeReturn.
DescriptionKnown problems Commands execution handlingIt's mandatory to verify error's code returned by any command or execution called by a shell script.
Description : Parseur behaviour becomes inaccurate when reading a command execution.
Description : On a pipiline, where the first function hsouldn't be verified and that there is only one function to verify in the pipe line, the violation message is the one intended to simples functions. Also, raising false positive on || use.
Code example :
grep "Date :" $ficresarc | awk '{print $3}' > datejul.tmpcd -- "$idir" || { echo >&2 can not cd to "$idir"; exit 1; }Description : The checker raise a violation when the test returned isn't like if [ $? -eq 0].
Description : The last violation detected by the checker on a file is set on the previous line of the violation.
Code example :
cd testdir
date +%d_%m_%y > newfile
retour=$?
ls
Description : The checker is not handling some types of functions declaration. The problem is the same one as defined for several rules in #49 . This might also be the reason a false positive violation raise when a function name isn't clearly defined.
Description : The checker raises false positive on export use.
Code example : export –f funcName
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4