gzencode in PHP-5.4 behaves differently than in previous versions.
I outlined the reasoning in the comment from 2009-03-03 22:11 UTC
at http://bugs.php.net/47178
Any comments?
Mike
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
hi Mike,
On Fri, Oct 28, 2011 at 10:59 AM, Michael Wallner wrote:
> gzencode in PHP-5.4 behaves differently than in previous versions.
> I outlined the reasoning in the comment from 2009-03-03 22:11 UTC
> at http://bugs.php.net/47178
>
> Any comments?
As I never used this mode ever (FORCE_DEFLAT
Zitat von Pierre Joye :
On Thu, Oct 27, 2011 at 12:00 PM, Jan Schneider wrote:
I'm going to check with our Jenkins guru, but I'm wondering how such a VM
should look like. Should it contain a complete Jenkins instance, or just a
checkout of the Horde packages that you would run from your own
Hi,
It would be nice if we could begin with 5.3.9 asap. It is long over
due and there is already a very long list of bug fixes :) Any plan
already?
Cheers,
--
Pierre
@pierrejoye | http://blog.thepimp.net | http://www.libgd.org
--
PHP Internals - PHP Runtime Development Mailing List
To unsubsc
Hi,
Is it an expected behaviour ?
See attached test file.
EXPECTED OUTPUT
Strict Standards: Declaration of ObjChild::method() should be
compatible with that of ObjParent::method() in %s on line 15
Strict standards: Declaration of ObjChild::__construct() should be
compatible with that
Am 28.10.2011 10:59, schrieb Michael Wallner:
> gzencode in PHP-5.4 behaves differently than in previous versions.
> I outlined the reasoning in the comment from 2009-03-03 22:11 UTC
> at http://bugs.php.net/47178
as long gzdecode() can decode stored data from previous versions
without destroy t
Ok it's a documented behaviour, I should read more carefully.
http://php.net/manual/en/language.oop5.decon.php
Unlike with other methods, PHP will not generate an E_STRICT level
error message when __construct() is overridden with different parameters
than the parent __construct() method has.
Bu
Hi Jean-Sebastien,
I'd say this is a harder-to-grasp concept and leads to this common
misconception.
Have a look here, particularly at my reply in the comments section:
http://devzone.zend.com/article/15273
In a nutshell, ctors (constructors) are not subject to LSP (liskov sub.
principle) b
To me, the interface found at https://wiki.php.net/rfc/splclassloader is
strange :
first, to be consistent with PSR-0, why allow changing the extension where
PSR-0 states that the only valid one is ".php"?
Why also have an interface to change the namespace separator?
Concerning userland specializ
On 2011-10-28, Nicolas Grekas wrote:
> About PSR-0 and applying the same reasoning, I don't understand why
> the underscore in the namespace part is not replaced by a directory
> separator: because of it's class to path transformation, PSR-0 forbids
> having two different classes named A\B_C and
Am 28.10.11 17:29, Reindl Harald schrieb:
> Am 28.10.2011 10:59, schrieb Michael Wallner:
>> gzencode in PHP-5.4 behaves differently than in previous versions.
>> I outlined the reasoning in the comment from 2009-03-03 22:11 UTC
>> at http://bugs.php.net/47178
> as long gzdecode() can decode stored
11 matches
Mail list logo