Sorry if this was already suggested before: for people stuck on legacy
applications and without money to upgrade (e.g. charities, user
groups) a PECL extension would at least provide a way to survive.
Forcing people to upgrade doesn't sound like an improvement but more
of a way to push people away
I see what you are trying to achieve, but I hope this will never make into
PHP mainly for impact on readability. I'd like to quote Eric Armstrong, a
passionate Java/Ruby dev:
> I decry their very existence. They are the ultimate condemnation of
static
> type checking--because their very addition
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
Hi,
nice work, out of curiosity I tried on a VM with 24 virtual cores:
Sequential new phpruntests: 29.6 seconds
Parallel -z 4: 12.1 - 12.3 secs
Parallel -z 8: 10.6 - 10.9 secs
Parallel -z 16: 10.6 - 11.3 secs
Parallel -z 24: 10.9 - 11.7 secs
Btw I'm seeing this error:
PHP Warning: Invalid arg
Hi,
I had a possible use case while working with an application registry. Any
model could "get a copy" of it to read application settings or retrieve a
resource. However if a model by mistake changed a property, it would
modify the original object without going through proper setters... A quick
> On Sun, May 6, 2012 at 11:47 AM, Laruence wrote:
> > On Sun, May 6, 2012 at 8:40 AM, Devis Lucato wrote:
> >> Hi,
> >>
> >> I stumbled upon this code while working with a variable passed by
> >> reference, I was wondering if someone could provide s
Hi,
I stumbled upon this code while working with a variable passed by
reference, I was wondering if someone could provide some feedback before
raising a ticket, just in case PHP (5.3.6) is doing what it's supposed to
do.
In the code below I would expect "catch" to change the variable as
an assignm
