Hi all,
Following patch against master
https://gist.github.com/yohgaki/6198611
implements FR #17860
https://bugs.php.net/bug.php?id=17860
This patch removes unneeded session writes. i.e. session data
has not changed, just skip write and improve performance.
Although it is safe to remove unnee
Hey Leigh,
I disagree that it suggests evaluation, but it could easily be a personal
interpretation thing. In my interpretation, when looking at use
statements, I know nothing is being evaluated. Symbols are being imported
into the namespace. How likely is it that baz returns something that can
Hi Stas,
On Sat, Aug 10, 2013 at 1:53 AM, Stas Malyshev wrote:
> We can also take some responsibility for making it easier to
> upgrade
>
That's the reason why I proposed adding "php_serialize" to 5.5.
Even if there are very few users may have problem with new serializer,
it would be good to pro
Hi Stas,
On Sat, Aug 10, 2013 at 1:53 AM, Stas Malyshev wrote:
> > As I wrote, there is no real BC issue as it's just a matter of ini
> setting.
>
> There is a BC issue if you need an ini setting. You keep dismissing it
> but if it affected the app your business relates on it'd be a major
> probl
On Aug 8, 2013 9:31 PM, "Daniel Bingham"
wrote:
>
> Hey Igor,
>
> I love the RFC, but how about:
>
> use bar\baz() as baz;
>
> As an alternative to "use function". Still new syntax, but a little less
> wordy.
The parenthesis add the feeling that it should be evaluated imho, I.e. the
result of th
Hi!
> As I wrote, there is no real BC issue as it's just a matter of ini setting.
There is a BC issue if you need an ini setting. You keep dismissing it
but if it affected the app your business relates on it'd be a major
problem if on upgrade your app breaks and you need to scour release
notes to
> Blaming the users is simply not acceptable!
That actually depends on the organization's focus. I, for one, will gladly
blame users when they don't care when their software is deprecated. Using
deprecated software is their risk, not ours, especially when they are not
keeping in close contact wi
Yasuo Ohgaki wrote:
If users aren't reading release note of minor version up, then it is users'
fault,
not ours. If it is, we cannot release new PHP.
MANY users don't even know that their hosting has been changed until their sites
stop working ... This happens a lot more often now than it eve
Hi Lester,
On Fri, Aug 9, 2013 at 6:29 PM, Lester Caine wrote:
> Leigh wrote:
>
>> How php_serialize would cause BC issues for PHP users?
>>
>> Not everyone uses PHP in the way you would expect. Just how many sites
>> out there
>> do you think use PHPs session functionality? I'd go for hundr
Leigh wrote:
How php_serialize would cause BC issues for PHP users?
Not everyone uses PHP in the way you would expect. Just how many sites out there
do you think use PHPs session functionality? I'd go for hundreds of millions,
and that's a pretty big target to hit.
If you session_encode() s
Hi Leigh,
On Fri, Aug 9, 2013 at 5:28 PM, Leigh wrote:
> On 8 August 2013 23:31, Yasuo Ohgaki wrote:
>
>>
>> How php_serialize would cause BC issues for PHP users?
>>
>
> Not everyone uses PHP in the way you would expect. Just how many sites out
> there do you think use PHPs session functionali
On 8 August 2013 23:31, Yasuo Ohgaki wrote:
>
> How php_serialize would cause BC issues for PHP users?
>
Not everyone uses PHP in the way you would expect. Just how many sites out
there do you think use PHPs session functionality? I'd go for hundreds of
millions, and that's a pretty big target t
Ferenc Kovacs wrote:
ps: on a related note, somehow I got the feeling that Lester complaining
that E_STRICT errors fataling/crashing the application migrated to PHP 5.4
was related to this problem, and I'm a bit sad that we didn't managed to
figure this out back then.
I think I'm hitting the sa
13 matches
Mail list logo
