| The whole reason we use these member prefixes is so that the
| tree is actually greppable. tcp_sock is the way it is because
| we never enforced this useful policy back when it was originally
| created.
|
| If you use short member names, it becomes eventually impossible
| to grep for "->foo" and have it not match a ton of crap you
| are completely not interested in. Using a prefix creates a
| struct member namespace, and thus fixes that problem.
|
Ok, but this creates two problems at another end:
1/ as it is, the code is very hard to read, since 80% of expressions
are taken up by the repetitive `hc{r,t}x->ccid{2-4}_hc_{r,t}x_';
2/ there are many expressions which involve computations involving
two and more field members. This almost inevitably creates
unwieldy multiline expressions.
These structs affect a subset of DCCP only, and are always preceded
either by "hctx->..." or "hcrx->...". This is a consistent convention.
With regard to being greppable,
* cscope was found to work with the short identifiers,
* have not tested ctags, here it may indeed be that there
are multiple matches,
* most of the source code is confined to net/dccp (the only
exception is include/linux/{dccp,tfrc}.h).
These two patches didn't come out of a personal whim: over the past
6 months this was discussed several times on dccp@vger, each time
people confirmed that the identifiers were too long. There was clear
agreement in this regard.
If you still find the above unacceptable with regard to the policy,
is there an alternative/compromise which would satisfy both goals?
Gerrit
--
To unsubscribe from this list: send the line "unsubscribe dccp" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
