| Package home | Report new bug | New search | Development Roadmap | Status: Open | Feedback | All | Closed Since Version 1.2.6 |
| Bug #5654 | 'Passing by reference' notice under PHP 4.4.0 | ||
|---|---|---|---|
| Submitted: | 2005-10-11 05:46 UTC | Modified: | 2006-12-24 14:33 UTC |
| From: | vladimir dot shapiro at michel-consulting dot de | Assigned: | farell |
| Status: | Closed | Package: | HTML_Progress |
| PHP Version: | 4.4.0 | OS: | Unix |
| Roadmaps: | (Not assigned) | ||
[2005-10-11 05:46 UTC] vladimir dot shapiro at michel-consulting dot de
Description:
------------
After upgrade my PHP up to 4.4.0 I get the follwoing notice
Notice: Only variables should be assigned by reference in /usr/lib/php/HTML/Progress.php on line 1118
Removing the passing by reference on the line 1118 seems to solve the problem. Anyway there are a lot of similar parts of code that should be checked.
More on topic "Memory corruptions with references":
http://www.php.net/release_4_4_0.php
Test script:
---------------
<?php
require_once 'HTML/Progress.php';
$progress_bar = new HTML_Progress();
$progress_bar->setAnimSpeed(100);
$progress_bar->setIncrement(10);
$progress_bar->setBorderPainted(true);
$progress_bar->setStringPainted(true);
$GLOBALS['extraCSS'] = $progress_bar->getStyle();
$GLOBALS['extraJS'] = $progress_bar->getScript();
?>
Expected result:
----------------
no notice (E_ALL safe output)
Actual result:
--------------
Notice: Only variables should be assigned by reference in /usr/lib/php/HTML/Progress.php on line 1118
Comments
[2005-10-15 06:22 UTC] farell
**************************
Hi Vladimir,
As this fix, is not so complex (removed only ampersand at line 1118 of Progress.php), it was only fixed into CVS until next public release (planned for November 1st).
regards
Laurent
[2005-10-15 06:23 UTC] farell
This bug has been fixed in CVS.
If this was a documentation problem, the fix will appear on pear.php.net by the end of next Sunday (CET).
If this was a problem with the pear.php.net website, the change should be live shortly.
Otherwise, the fix will appear in the package's next release.
Thank you for the report and for helping us make PEAR better.