Reviewed by Ojan Vafai.
Augment style guidelines about meaningless parameters from text the unwritten rules email.
https://bugs.webkit.org/show_bug.cgi?id=55275
* coding/coding-style.html:
git-svn-id: https://svn.webkit.org/repository/webkit/trunk@83127
268f45cc-cd09-0410-ab3c-
d52691b4dbfc
+2011-04-06 David Levin <levin@chromium.org>
+
+ Reviewed by Ojan Vafai.
+
+ Augment style guidelines about meaningless parameters from text the unwritten rules email.
+ https://bugs.webkit.org/show_bug.cgi?id=55275
+
+ * coding/coding-style.html:
+
2011-04-05 Yury Semikhatsky <yurys@chromium.org>
Unreviewed. Add Web Inspector stack trace, pause on exception and window.onerror
</pre>
</li>
-<li>Leave meaningless variable names out of function declarations.
+<li>Leave meaningless variable names out of function declarations. A good rule of thumb is if the parameter type name contains the parameter name (without trailing numbers or pluralization), then the parameter name isn't needed. Usually, there should be a parameter name for bools, strings, and numerical types.
<h4 class="right">Right:</h4>
<pre class="code">
void setCount(size_t);
+
+void doSomething(ScriptExecutionContext*);
</pre>
<h4 class="wrong">Wrong:</h4>
<pre class="code">
void setCount(size_t count);
+
+void doSomething(ScriptExecutionContext* context);
</pre>
</li>