From: "Petteri Räty" <betelgeuse@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/libbash:master commit in: bashast/, coding_standard/
Date: Wed, 30 Mar 2011 12:48:05 +0000 (UTC) [thread overview]
Message-ID: <1f8f800cee198affb83f4c86206377ef3f66591e.betelgeuse@gentoo> (raw)
commit: 1f8f800cee198affb83f4c86206377ef3f66591e
Author: Mu Qiao <qiaomuf <AT> gentoo <DOT> org>
AuthorDate: Mon Mar 28 02:42:05 2011 +0000
Commit: Petteri Räty <betelgeuse <AT> gentoo <DOT> org>
CommitDate: Tue Mar 29 04:34:45 2011 +0000
URL: http://git.overlays.gentoo.org/gitweb/?p=proj/libbash.git;a=commit;h=1f8f800c
Add indentation rules for grammar and autotools
Use tabs(ts=4) for grammar and autotools related files. Fixed
current indentation.
---
bashast/bashast.g | 4 ++--
coding_standard/coding_standard.tex | 9 ++++++---
2 files changed, 8 insertions(+), 5 deletions(-)
diff --git a/bashast/bashast.g b/bashast/bashast.g
index d16ba5c..ef87271 100644
--- a/bashast/bashast.g
+++ b/bashast/bashast.g
@@ -509,8 +509,8 @@ name : NAME
//****************
COMMENT
- : (BLANK|EOL) '#' ~('\n'|'\r')* {$channel=HIDDEN;}
- ;
+ : (BLANK|EOL) '#' ~('\n'|'\r')* {$channel=HIDDEN;}
+ ;
//Bash "reserved words"
BANG : '!';
CASE : 'case';
diff --git a/coding_standard/coding_standard.tex b/coding_standard/coding_standard.tex
index 8230453..ba2e508 100644
--- a/coding_standard/coding_standard.tex
+++ b/coding_standard/coding_standard.tex
@@ -28,7 +28,7 @@ Header files must contain the appropriate ifndef header guard:
#ifndef FILENAME_H
#define FILENAME_H
-/*
+/*
code
*/
@@ -76,7 +76,10 @@ Member variables in a class should have the following comment block:
\section{Program code}
\subsection{Indentation}
Every line inside of a code block should be indented for easier readability.\\
-Tabs should not be used for indentation, only spaces. Indentation width will be two spaces.
+Tabs should not be used for indentation, only spaces. Indentation width will be two spaces. \\
+Tabs should be used for ANTLR grammar because antlrworks automatically generate tabs. \\
+Tabs should also be used for autotools related files(Makefile.am, configure.ac, etc). \\
+Use ts=4 for indentation.
\subsection{Naming conventions}
The name of a variable, function, class, or struct should be obvious from it's name.\\
Names will use underscored names not mixed case.\\
@@ -135,4 +138,4 @@ return my_list.size();
return (index<max_index? index : max_index);
\end{verbatim}
-\end{document}
\ No newline at end of file
+\end{document}
next reply other threads:[~2011-03-30 12:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-30 12:48 Petteri Räty [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-04-20 14:04 [gentoo-commits] proj/libbash:master commit in: bashast/, coding_standard/ Petteri Räty
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1f8f800cee198affb83f4c86206377ef3f66591e.betelgeuse@gentoo \
--to=betelgeuse@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox