Re: [PHP-DEV] [RFC] Remove calls with incompatible Context

On 07/30/2012 01:32 PM, Gustavo Lopes wrote: 3. There are other low-cost alternatives, namely the obvious one: pass the object via an extra parameter instead of operating on $this directly and unconditionally. This is really easy to do. This kind of thing should be mentioned in the RFC. C

Re: [PHP-DEV] [RFC] Remove calls with incompatible Context

Em Mon, 30 Jul 2012 21:11:58 +0200, Todd Ruth escreveu: On Mon, 2012-07-30 at 19:31 +0200, Gustavo Lopes wrote: https://wiki.php.net/rfc/incompat_ctx An RFC for deprecating and removing $this from incompatible context. Comments are welcome. I'm just a user, but I'd like to beg that the

Re: [PHP-DEV] [RFC] Remove calls with incompatible Context

Em Mon, 30 Jul 2012 19:42:59 +0200, Will Fitch escreveu: I think this is a good idea. I agree with the intention of throwing E_DEPRECATED in 5.5, but what do you propose happen afterwards? Throw a fatal error? I would just like to make "removing (in the next version)" a little more defini

Re: [PHP-DEV] [RFC] Remove calls with incompatible Context

On Mon, Jul 30, 2012 at 3:11 PM, Todd Ruth wrote: > On Mon, 2012-07-30 at 19:31 +0200, Gustavo Lopes wrote: > > https://wiki.php.net/rfc/incompat_ctx > > > > An RFC for deprecating and removing $this from incompatible context. > > > > Comments are welcome. > > > > -- > > Gustavo Lopes > > I'm jus

Re: [PHP-DEV] [RFC] Remove calls with incompatible Context

On Mon, 2012-07-30 at 19:31 +0200, Gustavo Lopes wrote: > https://wiki.php.net/rfc/incompat_ctx > > An RFC for deprecating and removing $this from incompatible context. > > Comments are welcome. > > -- > Gustavo Lopes I'm just a user, but I'd like to beg that the feature not be removed, at lea

Re: [PHP-DEV] [RFC] Remove calls with incompatible Context

Gustavo, On Mon, Jul 30, 2012 at 1:31 PM, Gustavo Lopes wrote: > https://wiki.php.net/rfc/**incompat_ctx > > An RFC for deprecating and removing $this from incompatible context. > > Comments are welcome. A few points. 1. Finally! It's caused a lot of WTF

Re: [PHP-DEV] [RFC] Remove calls with incompatible Context

I think this is a good idea. I agree with the intention of throwing E_DEPRECATED in 5.5, but what do you propose happen afterwards? Throw a fatal error? I would just like to make "removing (in the next version)" a little more definitive. On Mon, Jul 30, 2012 at 1:31 PM, Gustavo Lopes wrote: > h

[PHP-DEV] [RFC] Remove calls with incompatible Context

https://wiki.php.net/rfc/incompat_ctx An RFC for deprecating and removing $this from incompatible context. Comments are welcome. -- Gustavo Lopes -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php

Re: [PHP-DEV] bug on bc math?

Hi! >but on the hand, we may also consider this as a bug, behavior not > act like the doc said :) If the library we are wrapping behaves in certain way, our function should behave in the same way. If docs say otherwise, docs should be fixed. -- Stanislav Malyshev, Software Architect SugarC

Re: [PHP-DEV] Bringing users along ...

On 07/30/2012 01:02 AM, Lester Caine wrote: > Having just been helping another unsophisticated user, the growing > problem of incompatibility between versions is starting to hit harder. > So can developers please start taking a little more care with the > support of existing users! Lester, we get

Re: [PHP-DEV] bug on bc math?

On Mon, Jul 30, 2012 at 9:52 PM, Laruence wrote: > Hi: > > I'd like mark this as a doc problem, see the comment of the bcmatch lib: > > /* The multiply routine. N2 times N1 is put int PROD with the scale of >the result being MIN(N2 scale+N1 scale, MAX (SCALE, N2 scale, N1 scale)). >*/ >

Re: [PHP-DEV] bug on bc math?

Hi: I'd like mark this as a doc problem, see the comment of the bcmatch lib: /* The multiply routine. N2 times N1 is put int PROD with the scale of the result being MIN(N2 scale+N1 scale, MAX (SCALE, N2 scale, N1 scale)). */ void bc_multiply (bc_num n1, bc_num n2, bc_num *prod, int s

Re: [PHP-DEV] Re: Generators in PHP

2012/7/28 Rasmus Lerdorf : > Very early versions of PHP v1 actually had distinct list, map and set > implementations but I replaced those early on with a unified hybrid > ordered map implementation and just called it the "Array" type. The > thinking was that in almost all situations in a Web app, a

[PHP-DEV] bug on bc math?

Hi, before raising a bug I was wondering if anyone noticed this odd behavior in BC math functions ? Actual php -r "echo bcmul('1.1', '9.0', 5);" ==> 9.90 php -r "bcscale(5); echo bcmul('1.1', '9.0');" ==> 9.90 php -r "bcscale(5); echo bcadd('8.9', '1.0');" ==> 9.9 Expected php -r "echo bc

[PHP-DEV] VCS Account Rejected: bspim rejected by bjori

Nuked bspim -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php

Re: [PHP-DEV] Bringing users along ...

Adam Harvey wrote: What, specifically, have you found that isn't covered in the release notes and/or migration guide for PHP 5.3 and 5.4? Documentation bugs would be awesome here. (Patches would be even more awesome.) It's hard to improve this without detailed information, since the migration gu

Re: [PHP-DEV] Bringing users along ...

On 30 July 2012 16:02, Lester Caine wrote: > Moving people from 5.2 is probably going to be as bad as killing off PHP4 > and 4.6% of sites are still using that! But the main problem starting to > happen now is that developers are upgrading projects to use 5.3 and 5.4 > features, but simply assumin

[PHP-DEV] Bringing users along ...

Having just been helping another unsophisticated user, the growing problem of incompatibility between versions is starting to hit harder. So can developers please start taking a little more care with the support of existing users! From w3techs ... http://w3techs.com/technologies/details/pl-php/

[PHP-DEV] xml ext and & entities

Hi! I was running PHP tests on my freshly installed CentOS instance and I noticed that two XML tests were failing: ext/xml/tests/bug35447.phpt and ext/xml/tests/xml011.phpt. Looks like for some reason XML parser when parsing something like this: This & that - produces empty string instead of "&" w