Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Attached patch fixes what I am sure are simple typographical errors:
--- a/includes/bootstrap.inc
+++ b/includes/bootstrap.inc
@@ -418,7 +418,7 @@ abstract class DrupalCacheArray implements ArrayAccess {
* Start the timer with the specified name. If you start and stop the same
* timer multiple times, the measured intervals will be accumulated.
*
- * @param name
+ * @param $name
* The name of the timer.
*/
function timer_start($name) {
@@ -431,7 +431,7 @@ function timer_start($name) {
/**
* Read the current timer value without stopping the timer.
*
- * @param name
+ * @param $name
* The name of the timer.
* @return
* The current timer value in ms.
@@ -454,7 +454,7 @@ function timer_read($name) {
/**
* Stop the timer with the specified name.
*
- * @param name
+ * @param $name
* The name of the timer.
* @return
* A timer array. The array contains the number of times the timer has been
Comments
Comment #1
Lars Toomre CreditAttribution: Lars Toomre commentedWhile you are in there, could you add a blank line before the @return doc statements? Thanks.
Comment #2
pillarsdotnet CreditAttribution: pillarsdotnet commented@Lars Toomre
Done, but now it probably won't get reviewed until after November 1st; sigh.
Comment #3
Lars Toomre CreditAttribution: Lars Toomre commentedThank you @pillarsdotnet. As is this looks good to go.
On a side note, do you know if the @param type hinting proposal for docblocks has been approved yet? If so, this patch includes a number of places where that type of docblock change also needs to be implemented.
Comment #4
pillarsdotnet CreditAttribution: pillarsdotnet commented@Lars Toomre
Feel free to RTBC; you're obviously qualified and this is a trivial docs-only change.
You can join the discussion at Should all @param data types be documented?
And #1290258: The data type should be explicitly stated for all Drupal core @param and @return documentation.
Comment #5
jhodgdonPLEASE don't do a whole file at once, just do the functions mentioned in the issue (3 functions, not the whole file!!!!!!!). Then we can actually fix the doc that has problems.
Comment #6
pillarsdotnet CreditAttribution: pillarsdotnet commentedWhatever. Re-uploading the original patch. Y'all argue amongst yourselves as to which way you want it.
Comment #7
jhodgdonThere's a sweet spot between fixing the blank line problems in the 3 functions named in the issue, and fixing the whole file...
Comment #8
pillarsdotnet CreditAttribution: pillarsdotnet commentedFine, but when I submit separate patches for each of the other functions, both you and webchick will complain. She's already complained about the fact that I submitted separate patches for separate files as I found similar problems in each.
I really wish y'all would reach a consensus on these things. And publish it somewhere so I can re-read it when I forget.
Comment #9
pillarsdotnet CreditAttribution: pillarsdotnet commentedComment #10
jhodgdonSee http://drupal.org/node/1295500#comment-5068622 regarding the consensus question. I do think that the ideas there represent consensus as in "how things have been going in the last year or two", and sorry they weren't written down somewhere for you.
Anyway, thanks, this patch is good to go for d7/8.
Comment #11
webchickCommitted and pushed to 8.x and 7.x.