[Telepathy-commits] [telepathy-gabble/master] check-c-style.sh: be strict about formatting of casts and pointer types
Simon McVittie
simon.mcvittie at collabora.co.uk
Tue Aug 19 10:53:22 PDT 2008
20080721131854-53eee-9eb995b5a0a4e610900b5c0201169a7a9b3312ec.gz
---
tools/check-c-style.sh | 20 ++++++++++++++++++++
1 files changed, 20 insertions(+), 0 deletions(-)
diff --git a/tools/check-c-style.sh b/tools/check-c-style.sh
index 357fdb3..6ed106c 100644
--- a/tools/check-c-style.sh
+++ b/tools/check-c-style.sh
@@ -24,6 +24,26 @@ then
fail=1
fi
+if grep -En '[(][[:alnum:]_]+ ?\*[)][(]?[[:alpha:]_]' "$@"; then
+ echo "^^^ Our coding style is to have a space between a cast and the "
+ echo " thing being cast"
+ fail=1
+fi
+
+# this only spots casts
+if grep -En '[(][[:alnum:]_]+\*+[)]' "$@"; then
+ echo "^^^ Our coding style is to have a space before the * of pointer types"
+ echo " (regex 1)"
+ fail=1
+fi
+# ... and this only spots variable declarations and function return types
+if grep -En '^ *(static |const |)* *[[:alnum:]_]+\*+([[:alnum:]_]|;|$)' \
+ "$@"; then
+ echo "^^^ Our coding style is to have a space before the * of pointer types"
+ echo " (regex 2)"
+ fail=1
+fi
+
if test -n "$CHECK_FOR_LONG_LINES"
then
if egrep -n '.{80,}' "$@"
--
1.5.6.3
More information about the Telepathy-commits
mailing list