Implementation of the rule COM.PRES.Indent.
DescriptionKnown problems Awk command handlingCode indentation must be spaces (no tabulation).
Description : The checker raises violation when using awk
Description : Behaviour of the checker becomes inaccurate when reading quotes or double quotes.
Description : Case statements is not handled correctly, which leads it to raise false positives.
Description : The checker raises false positives after commented lines. This problem might be due by ELSE, CONT, currentPos and desiredPos in the lex.
Description : It seems that the number of {} braces accounting cause crashes of the anaylsis. Might come from the item +([0-9]) of the case. For instance the code beetween braces in :[[ $? != 0 ]] && { echo >&2 the required \"message\" command is not in your PATH; exit 1; }
Description : Bad increasing of indentation is not handled by the checker. For example :
ma_fonction_affine ()
{
if [ $# -ne 3 ]
then
my_function=$code_error_nbargs
else
printf "Calling : p1=%s p2=%s p3=%s\n" $1 $2 $3
# operation : y = ax + b
let y=$1*$2+$3
printf "y=%s\n" $y
my_function=$y
fi
}
Description : The checker is not handling some types of functions declaration. The problem is the same one as defined for several rules in #49 .
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