'clone' is a reserved keyword introduced in PHP version 5.0 and cannot be invoked as a function

Confirmed this fixes the issue and is the proper usage of clone as per:

http://php.net/manual/en/language.oop5.cloning.php

Let's get testing bot for 5.6 then
https://www.drupal.org/pift-ci-job/132748

Lets include this in the next release. Rerolled.

Tested the patch manually and it's working fine.
Also it's pass in automated custom test: https://www.drupal.org/pift-ci-job/642296

As Clone is reserved keyword it's good to not use it as function.
http://php.net/manual/en/reserved.keywords.php

Tested the patch manually and it's working fine.
Also it's pass in automated custom test: https://www.drupal.org/pift-ci-job/642296

As Clone is reserved keyword it's good to not use it as function.
http://php.net/manual/en/reserved.keywords.php

Bumping to 2.11.

Committed.

The patches work for version 2.10, however, for the oldest version like 2.9, it needs to do a little change, instead of using $argument->min_date use $argument->max_date as shown below.

@@ -279,9 +279,9 @@ function query() {
          ...
         else {
-          $this->view->date_info->prev_date = clone($argument->min_date);
+          $this->view->date_info->prev_date = clone $argument->min_date;
           date_modify($this->view->date_info->prev_date, '-1 ' . $argument->date_handler->granularity);
-          $this->view->date_info->next_date = clone($argument->max_date);
+          $this->view->date_info->next_date = clone $argument->max_date;
           date_modify($this->view->date_info->next_date, '+1 ' . $argument->date_handler->granularity);
         }

@aritomelo: Hopefully you won't have to keep using 2.9 and we'll be able to fix any bugs that are preventing you from updating :)