Change comment style to use @foo rather than FOO
... when referring to a function's parameter or a struct/union's member. The idea of using FOO comes from the GNU coding standards: The comment on a function is much clearer if you use the argument names to speak about the argument values. The variable name itself should be lower case, but write it in upper case when you are speaking about the value rather than the variable itself. Thus, "the inode number NODE_NUM" rather than "an inode". Upcasing names is problematic for a case-sensitive language like C, because it can create ambiguity. Moreover, it's too much shouting for my taste. GTK-Doc's convention to prefix the identifier with @ makes references to variables stand out nicely. The rest of the GTK-Doc conventions make no sense for us, however. Signed-off-by: Markus Armbruster <armbru@pond.sub.org>
This commit is contained in:
parent
5cff5022a9
commit
9f25de3dce
77 changed files with 633 additions and 633 deletions
|
@ -745,8 +745,8 @@ att_ask_offense(int combat_mode, struct combat *off, struct combat *def,
|
|||
}
|
||||
|
||||
/*
|
||||
* Return path cost for ATTACKER to enter sector given by DEF.
|
||||
* MOBTYPE is a mobility type accepted by sector_mcost().
|
||||
* Return path cost for @attacker to enter sector given by @def.
|
||||
* @mobtype is a mobility type accepted by sector_mcost().
|
||||
*/
|
||||
static double
|
||||
att_mobcost(natid attacker, struct combat *def, int mobtype)
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue