Re: svn: /phpdoc/en/trunk/appendices/ migration53.xml
| From: | Philip Olson | Date: | Tue, 21 Sep 2010 16:48:00 +0000 |
| Subject: | Re: svn: /phpdoc/en/trunk/appendices/ migration53.xml | ||
| References: | 1 2 3 | Groups: | php.doc.cvs |
| Request: | Send a blank email to doc-cvs+get-7145@lists.php.net to get a copy of this message | ||
On Sep 21, 2010, at 9:36 AM, Richard Quadling wrote:
> On 21 September 2010 17:21, Philip Olson <philip@roshambo.org> wrote:
>>
>> On Sep 21, 2010, at 9:18 AM, Mark Skilbeck wrote:
>>
>>> markskilbeck Tue, 21 Sep 2010 16:18:00 +0000
>>>
>>> Revision:
>>> http://svn.php.net/viewvc?view=revision&revision=303646
>>>
>>> Log:
>>> #52248 {} is *not* deprecated
>>>
>>> Bug: http://bugs.php.net/52248 (Open) PDO::prepare()
>>> never return false on failure
>>>
>>> Changed paths:
>>> U phpdoc/en/trunk/appendices/migration53.xml
>>>
>>> Modified: phpdoc/en/trunk/appendices/migration53.xml
>>> ===================================================================
>>> --- phpdoc/en/trunk/appendices/migration53.xml 2010-09-21 16:13:24 UTC (rev
>>> 303645)
>>> +++ phpdoc/en/trunk/appendices/migration53.xml 2010-09-21 16:18:00 UTC (rev
>>> 303646)
>>> @@ -691,12 +691,6 @@
>>> Call-time pass-by-reference is now deprecated.
>>> </simpara>
>>> </listitem>
>>> - <listitem>
>>> - <simpara>
>>> - The use of <literal>{}</literal> to access string offsets is
>>> deprecated.
>>> - Use <literal>[]</literal> instead.
>>> - </simpara>
>>> - </listitem>
>>> </itemizedlist>
>>> </section>
>>
>> Says who? In the very least this should be discussed on a mailing list first.
>>
>> Regards,
>> Philip
>>
>
> No E_DEPRECATED warning when using ...
<snip>
Yes, but this is a unique situation. The question should be "Why no E_DEPRECATED" first.
Currently the reasons are vague memories in the back of peoples minds with no official answer. We
need an official stance before changing the documentation. Some memories are "Keep it
deprecated but without the error" so... it's something we must finalize.
I'll bring it up on internals@ but in the meantime, please revert this change.
Regards,
Philip