Confirmed users, Bureaucrats and Sysops emeriti
969
edits
Quantum/DOM: Difference between revisions
Jump to navigation
Jump to search
Runnable naming convention tweak
(Put the "Runnable naming convention" immediately after the "Obtaining the correct group" section since both go together to get the "labels" for a runnable) |
(Runnable naming convention tweak) |
||
| Line 46: | Line 46: | ||
* If the runnable is a method (created via some variant of NewRunnableMethod), then the class name and method name should form the name. <code>"nsDocument::UpdateVisibilityState"</code> is a good example. Namespaces should be omitted as before unless they're necessary. | * If the runnable is a method (created via some variant of NewRunnableMethod), then the class name and method name should form the name. <code>"nsDocument::UpdateVisibilityState"</code> is a good example. Namespaces should be omitted as before unless they're necessary. | ||
* If the runnable is a function created via NewRunnableFunction, follow the rule as if it were a class. | * If the runnable is a function created via NewRunnableFunction, follow the rule as if it were a class. | ||
If the runnable name would be ambiguous <i>and</i> it lives in an anonymous namespace, then make up a namespace that seems right. | |||
== Dispatching == | == Dispatching == | ||