Hi,
I was told (didn't verify) that this causes lots of trouble with PEAR
and other applications. We're in final RC phase of 5.3.7. I don't think
it is critical for 5.3.7 and I wonder whether we need it for 5.3 at all.
johannes
On Mon, 2011-07-04 at 14:55 +, Dmitry Stogov wrote:
dmitry
what kind of troubles do they see?
2011/7/7 Johannes Schlüter johan...@schlueters.de:
Hi,
I was told (didn't verify) that this causes lots of trouble with PEAR
and other applications. We're in final RC phase of 5.3.7. I don't think
it is critical for 5.3.7 and I wonder whether we need it for
On Thu, 2011-07-07 at 20:27 +0200, Pierre Joye wrote:
what kind of troubles do they see?
https://pear.php.net/bugs/bug.php?id=18656
Even if the Warning is good it's questionable for 5.3, especially during
RC.
(note that warnings not only cause the error being reported, which can
be switched off
Hi!
On 7/7/11 2:08 PM, Johannes Schlüter wrote:
On Thu, 2011-07-07 at 20:27 +0200, Pierre Joye wrote:
what kind of troubles do they see?
https://pear.php.net/bugs/bug.php?id=18656
Even if the Warning is good it's questionable for 5.3, especially during
RC.
Yes, I had problem with it too
felipe Thu, 07 Jul 2011 23:07:14 +
Revision: http://svn.php.net/viewvc?view=revisionrevision=313056
Log:
- Fixed bug #55156 (ReflectionClass::getDocComment() returns comment even
though the class has none)
Bug: https://bugs.php.net/55156 (Closed)
