ID: 24687
Comment by: waboring at 3gstech dot com
Reported By: nologic at pchome dot com dot tw
Status: Wont fix
Bug Type: Zend Engine 2 problem
Operating System: *
PHP Version: 5CVS
New Comment:
Fix your scripts? They weren't broken. php5 broke them. This is a
very common thing to be able to do a
return function_call_here()
I'm ashamed at the comments against fixing this. Basically being..this
is too hard, so you change instead. This is going to break a LOT of
people's code and will prevent me from moving to php5. Please fix
this.
Previous Comments:
------------------------------------------------------------------------
[2003-10-14 07:51:34] [EMAIL PROTECTED]
Fix your scripts.
------------------------------------------------------------------------
[2003-08-16 04:14:19] jan at horde dot org
Any idea yet if this will be fixed/addressed or should we start
converting scripts to not use referenced return type or build variables
that get returned?
------------------------------------------------------------------------
[2003-07-24 03:16:39] mikkel at linet dot dk
I have the same problem with PHP5 snap 200307240730, PEAR DB will not
work, as many functions has "&" in front of them. So a "return new
DB_Result" does not work.
Mayby this should only be a "notice" instead of a "fatal" error.
------------------------------------------------------------------------
[2003-07-22 11:53:29] [EMAIL PROTECTED]
Yes, it is quite complicated. You can only return variables by
reference, a function's return value is not something we can 'connect'
to...
------------------------------------------------------------------------
[2003-07-17 03:35:38] [EMAIL PROTECTED]
If you do it like this it works:
class TextSanitizer
{
function &htmlSpecialChars($text) {
$foo = preg_replace("/&/i", '&', htmlspecialchars($text,
ENT_QUOTES));
return $foo;
}
}
So would it really be *that* hard to make it work?
------------------------------------------------------------------------
The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
http://bugs.php.net/24687
--
Edit this bug report at http://bugs.php.net/?id=24687&edit=1
