So you're okay with substr($obj, 0, 3) giving you "Obj" ??
To me, that seems broken, regardless of whether we had it "working" in
the past.
-Andrei
On Jan 3, 2007, at 10:58 AM, Antony Dovgal wrote:
On 01/03/2007 09:51 PM, Andrei Zmievski wrote:
Only in cases where people blindly pass objects where strings are
expected. It won't break anything for those objects that know how to
convert themselves.
It still see no reasons for this particular change in behavior.
It was allowed in the past and I'm sure it should be still okay to do
it as long as there are no technical reasons to prevent it, which I'm
unable to see.
On Dec 27, 2006, at 1:23 PM, Antony Dovgal wrote:
On 12/28/2006 12:12 AM, Andrei Zmievski wrote:
It's perfectly legal to do it in 5.2 and I don't see why PHP6 is
different.
IMO it's same as changing the E_RECOVERABLE to E_ERROR - users
won't have any way to "workaround" it, even though this was the
original intention of E_RECOVERABLE.
It is not the same. E_ERROR stops execution. Returning FAILURE from
convert_to_string() is simply a flag that lets calling code know
what happened.
Failure in zend_parse_parameters() means that function itself will
not be executed, which is a major change in behaviour and I don't
think we really want it.
--
Wbr, Antony Dovgal
--
Wbr, Antony Dovgal
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
