On 04/01/2015 09:15 AM, Dan Ackroyd wrote:
> Hi,
>
> I'd like to get people's feedback for the idea of making setlocale be
> either deprecated and to be removed eventually or just increasing the
> warning level against people using it.
>
> The short version of why we should do this is that setloc
On 01/04/15 22:11, Stanislav Malyshev wrote:
>> * mysqli::next_result() if there is no next result throws "There is no next
>> > result set"
> This I'm not sure should produce anything at all - it has the return
> value of false, should be good enough.
'Traditional' scanning of a result set on mos
Le 31/03/2015 23:47, Andrey Hristov a écrit :
On 1.04.2015 00:31, Rowan Collins wrote:
On 31 March 2015 21:23:56 GMT+01:00, Andrey Hristov
wrote:
So, if Zend can be optimized to quickly clean the execution
environment,
and easily switch between them, we can have a giant leap towards
concurren
On Thu, Apr 2, 2015 at 3:21 AM, Rasmus Lerdorf wrote:
> On 04/01/2015 09:15 AM, Dan Ackroyd wrote:
> > Hi,
> >
> > I'd like to get people's feedback for the idea of making setlocale be
> > either deprecated and to be removed eventually or just increasing the
> > warning level against people using
> De : Stanislav Malyshev [mailto:smalys...@gmail.com]
>
> > The questions here are:
> > * will this code break any code running with PHP before that patch?
> > * does this code change the language in any way?
>
> OK, so I think there's a misunderstanding here. What you describing is
> exactly my
Hi,
PHP 5.5.24RC1 is available for testing.
You can download it from
https://downloads.php.net/~jpauli/
The Windows binaries are available at http://windows.php.net/qa/
This release contains a number of bugfixes.
For the list of bugfixes that you can target in your
testing, please refer to the
Hello
PHP 5.6.8 RC1 is available for testing.
You can download it from
http://downloads.php.net/~tyrael/
The Windows binaries are available at http://windows.php.net/qa/
This release contains a number of bugfixes.
For the list of bugfixes that you can target in your
testing, please refer to th
Hi Julien,
I am unsure of the timing windows for things being committed to being
in a release, but it seems unfortunate to not have this included:
https://github.com/php/php-src/commit/86f983bd3ea13def42e36842e03f785d02d40a7f
cheers
Dan
--
PHP Internals - PHP Runtime Development Mailing List
T
On Thu, Apr 2, 2015 at 7:34 PM, Dan Ackroyd wrote:
> Hi Julien,
>
> I am unsure of the timing windows for things being committed to being
> in a release, but it seems unfortunate to not have this included:
>
>
> https://github.com/php/php-src/commit/86f983bd3ea13def42e36842e03f785d02d40a7f
>
> ch
Ferenc Kovacs wrote:
> this would also eliminate
> the confusion, that something is present in 5.6.27 but not in
> 5.5.40(because 5.6.27 was released after 5.5.40, and this new stuff will
> land in 5.5.41).
I think the solution to this is pretty clear, as Rowan put it:
Rowan Collins wrote:
> - On
On Thu, Apr 2, 2015 at 12:27 PM, Dan Ackroyd wrote:
> Ferenc Kovacs wrote:
> > this would also eliminate
> > the confusion, that something is present in 5.6.27 but not in
> > 5.5.40(because 5.6.27 was released after 5.5.40, and this new stuff will
> > land in 5.5.41).
>
> I think the solution to
On 2 April 2015 at 16:01, Keyur Govande wrote:
>
>
> To Rasmus's point, here's a PR for HHVM to provide a thread-safe setlocale
> implementation: https://github.com/facebook/hhvm/pull/4736/files
>
> It should be fairly easy to refactor the thread-safe-setlocale.(h/cpp) files
> for Zend.
Ok, that'
On 2 April 2015 at 12:24, Dan Ackroyd wrote:
> On 2 April 2015 at 16:01, Keyur Govande wrote:
>>
>>
>> To Rasmus's point, here's a PR for HHVM to provide a thread-safe setlocale
>> implementation: https://github.com/facebook/hhvm/pull/4736/files
>>
>> It should be fairly easy to refactor the thre
On Thu, Apr 2, 2015 at 1:50 PM, Adam Harvey wrote:
> On 2 April 2015 at 12:24, Dan Ackroyd wrote:
> > On 2 April 2015 at 16:01, Keyur Govande wrote:
> >>
> >>
> >> To Rasmus's point, here's a PR for HHVM to provide a thread-safe
> setlocale
> >> implementation: https://github.com/facebook/hhvm/
On Thu, Apr 2, 2015 at 3:55 PM, Ryan Pallas wrote:
>
>
> On Thu, Apr 2, 2015 at 1:50 PM, Adam Harvey wrote:
>
>> On 2 April 2015 at 12:24, Dan Ackroyd wrote:
>> > On 2 April 2015 at 16:01, Keyur Govande wrote:
>> >>
>> >>
>> >> To Rasmus's point, here's a PR for HHVM to provide a thread-safe
>
Adam Harvey wrote:
> What about just adding another function: setlocale_global(), or similar?
Do you mean setlocale would become the thread safe one, and
setlocale_global() would be the current behaviour? If so, that would
be a BC break for the small number of people who are deliberately
using set
On 04/02/2015 02:13 PM, Dan Ackroyd wrote:
> Adam Harvey wrote:
>> What about just adding another function: setlocale_global(), or similar?
>
> Do you mean setlocale would become the thread safe one, and
> setlocale_global() would be the current behaviour? If so, that would
> be a BC break for the
Hi everybody!
It seems there are a lot of (old) bug reports for unmaintained PECL
extensions. I wonder what the official stance is on that.
For instance, there is #57551[1], which has been "suspended" by Joe
Watkins recently. I'm not too happy with "suspending" those bug
reports, because they'r
Hi!
> It seems to me we are mixing two questions : can 'small
> self-contained' changes be introduced in a patch release, and how
> 'small' and 'self-contained' a change must be not to require an RFC ?
> It seems implicit that, once an RFC is written, it is not a 'small
> self-contained' change an
Hi!
> +1 This is exactly it. The longer older versions are "supported" the
> longer they remain in the wild.
5.3 is unsupported and still has over 40%. 5.2 is dead for 4 years by
now and still beats 5.5 by factor of more than 2. So I don't think just
unsupporting something will make a big differ
W dniu 2015-04-03 o 01:59, Christoph Becker pisze:
Hi everybody!
It seems there are a lot of (old) bug reports for unmaintained PECL
extensions. I wonder what the official stance is on that.
For instance, there is #57551[1], which has been "suspended" by Joe
Watkins recently. I'm not too happ
On Apr 3, 2015 11:55 AM, "Stanislav Malyshev" wrote:
>
> Hi!
>
> > +1 This is exactly it. The longer older versions are "supported" the
> > longer they remain in the wild.
>
> 5.3 is unsupported and still has over 40%. 5.2 is dead for 4 years by
> now and still beats 5.5 by factor of more than 2.
22 matches
Mail list logo
