PHP 5 Bug Database summary - http://bugs.php.net/
Num Status Summary (1228 total -- which includes 762 feature requests)
===[*General Issues]==
46779 Open Compilation failed in preg_replace for Unicode character
properties
==
PHP 6 Bug Database summary - http://bugs.php.net/
Num Status Summary (69 total -- which includes 31 feature requests)
===[*General Issues]==
26771 Suspended register_tick_funtions crash under threaded webservers
===
hi!
On Mon, Dec 8, 2008 at 12:50 PM, Rodrigo Saboya
<[EMAIL PROTECTED]> wrote:
> All links at http://windows.php.net/qa/ are 404.
Fixed, the files were there but a change I made in the scripts was
setting the wrong directory. Thanks for the head up!
Cheers,
--
Pierre
http://blog.thepimp.net |
Lukas Kahwe Smith wrote:
Hello!
Johannes has packaged PHP 5.3.0alpha3, which you can find here:
http://downloads.php.net/johannes/
Windows binaries thanks to Pierre, which are available here:
http://windows.php.net/qa/
Please test it carefully, and report any bugs in the bug system, but
only
Igor Feghali wrote:
> // NOTE: leaving the callback function empty is not desired. 0 and 0.0
> should not be skipped in the implode array !
> array_filter($arr, 'myfunc');
> implode('foo', $arr);
>
> against:
>
> implode('foo', $arr, true);
implode('foo', array_filter($arr, 'myfunc'));
Simple e
Hi.
Running 5.3.0alpha3 now and converting our codebase to the new
namespaces syntax. Works fine so far, the new name resolution rules are
very usable and lead to cleaner code so far. :)
Now I ran into a problem. We have a class extending ReflectionProperty,
and I got a complaint about the s
Should the 5.3 release be re-branched perhaps as well, since it too
has this problem?
On 7-Dec-08, at 1:33 PM, Marcus Boerger wrote:
Hello Ilia,
brilliant :-)
Sunday, December 7, 2008, 7:16:43 PM, you wrote:
I will be re-branching 5.2.7 with this revert for the purpose of
5.2.8
this w
hi,
On Mon, Dec 8, 2008 at 3:15 PM, Ilia Alshanetsky <[EMAIL PROTECTED]> wrote:
> Should the 5.3 release be re-branched perhaps as well, since it too has this
> problem?
I do not think it is necessary for 5.3. It is an alpha release after
all and seriously, anyone who plans to move to 5.3.0 and s
On Mon, Dec 8, 2008 at 15:24, Pierre Joye <[EMAIL PROTECTED]> wrote:
> hi,
>
> On Mon, Dec 8, 2008 at 3:15 PM, Ilia Alshanetsky <[EMAIL PROTECTED]> wrote:
>> Should the 5.3 release be re-branched perhaps as well, since it too has this
>> problem?
>
> I do not think it is necessary for 5.3. It is an
On Mon, Dec 8, 2008 at 4:06 PM, Hannes Magnusson
<[EMAIL PROTECTED]> wrote:
> On Mon, Dec 8, 2008 at 15:24, Pierre Joye <[EMAIL PROTECTED]> wrote:
>> hi,
>>
>> On Mon, Dec 8, 2008 at 3:15 PM, Ilia Alshanetsky <[EMAIL PROTECTED]> wrote:
>>> Should the 5.3 release be re-branched perhaps as well, sinc
2008/12/8 Pierre Joye <[EMAIL PROTECTED]>:
> On Mon, Dec 8, 2008 at 4:06 PM, Hannes Magnusson
> <[EMAIL PROTECTED]> wrote:
>> On Mon, Dec 8, 2008 at 15:24, Pierre Joye <[EMAIL PROTECTED]> wrote:
>>> hi,
>>>
>>> On Mon, Dec 8, 2008 at 3:15 PM, Ilia Alshanetsky <[EMAIL PROTECTED]> wrote:
Should
Hi,
let's take this to a new thread so it'S not hidden in other discussions:
On Mon, 2008-12-08 at 16:06 +0100, Hannes Magnusson wrote:
> > I do not think it is necessary for 5.3. It is an alpha release after
> > all and seriously, anyone who plans to move to 5.3.0 and still
> > relies on magic q
Hi!
According to the manual and the PHP source the signature is this:
public function getValue(stdclass $object)
Manual is unfortunately not exact in this point - true signature for it
is public function getValue([object $object]) - i.e. $object is not
required and if it's supplied, it does
On Mon, 2008-12-08 at 09:15 -0500, Ilia Alshanetsky wrote:
> Should the 5.3 release be re-branched perhaps as well, since it too
> has this problem?
The 5.3 alpha release is hopefully not used in production by anybody so
I don't think it's critical there. Maybe it motivates somebody to think
abo
On Mon, Dec 8, 2008 at 16:47, Johannes Schlüter <[EMAIL PROTECTED]> wrote:
> Hi,
>
> let's take this to a new thread so it'S not hidden in other discussions:
>
> On Mon, 2008-12-08 at 16:06 +0100, Hannes Magnusson wrote:
>> > I do not think it is necessary for 5.3. It is an alpha release after
>> >
On Mon, Dec 8, 2008 at 4:47 PM, Johannes Schlüter <[EMAIL PROTECTED]> wrote:
> Hi,
>
> let's take this to a new thread so it'S not hidden in other discussions:
>
> On Mon, 2008-12-08 at 16:06 +0100, Hannes Magnusson wrote:
>> > I do not think it is necessary for 5.3. It is an alpha release after
>>
2008/12/8 Johannes Schlüter <[EMAIL PROTECTED]>:
> Hi,
>
> let's take this to a new thread so it'S not hidden in other discussions:
>
> On Mon, 2008-12-08 at 16:06 +0100, Hannes Magnusson wrote:
>> > I do not think it is necessary for 5.3. It is an alpha release after
>> > all and seriously, anyone
Hello Pierre,
Monday, December 8, 2008, 4:08:49 PM, you wrote:
> On Mon, Dec 8, 2008 at 4:06 PM, Hannes Magnusson
> <[EMAIL PROTECTED]> wrote:
>> On Mon, Dec 8, 2008 at 15:24, Pierre Joye <[EMAIL PROTECTED]> wrote:
>>> hi,
>>>
>>> On Mon, Dec 8, 2008 at 3:15 PM, Ilia Alshanetsky <[EMAIL PROTECTED
On Mon, Dec 8, 2008 at 16:57, Pierre Joye <[EMAIL PROTECTED]> wrote:
> On Mon, Dec 8, 2008 at 4:47 PM, Johannes Schlüter <[EMAIL PROTECTED]> wrote:
>>
>> When dropping magic_quotes the hosting company can do one of two things:
>>
>> a) not update to 5.3 so we either have to maintain 5.2 for some ti
Hi,
On Mon, 2008-12-08 at 16:03 +, Richard Quadling wrote:
> But I also understand it is pretty shitty to miss a 1 liner (magic
> quotes removed) and find everything broken and then to be told
> RTFM/RTFCL.
There's a difference between this and other breaks: Most other BC breaks
change the be
Hello Pierre,
Monday, December 8, 2008, 4:57:17 PM, you wrote:
> On Mon, Dec 8, 2008 at 4:47 PM, Johannes Schlüter <[EMAIL PROTECTED]> wrote:
>> Hi,
>>
>> let's take this to a new thread so it'S not hidden in other discussions:
>>
>> On Mon, 2008-12-08 at 16:06 +0100, Hannes Magnusson wrote:
>>>
Hello Stanislav,
Monday, December 8, 2008, 4:50:52 PM, you wrote:
> Hi!
>> According to the manual and the PHP source the signature is this:
>> public function getValue(stdclass $object)
> Manual is unfortunately not exact in this point - true signature for it
> is public function getValue([o
Pierre Joye escribió:
> I would even like to drop it (and the other things as well) in 5.3.0 :)
Yes, please :) but throw an error when use is detected.
--
"We have art in order not to die of the truth" - Friedrich Nietzsche
Cristian Rodríguez R.
Platform/OpenSUSE - Core Services
SUSE LINUX Pr
I don't safe stuff relying on magic_quotes is safe but kicking it will
open up way more attack vectors... :-(
In my opinion, this isn't about opening attack vectors (one hole is
all it takes, so they're probably already vulnerable), but removing
mqgpc without fair warning to end users could
On 8 Dec 2008, at 08:18, Hannes Magnusson wrote:
On Mon, Dec 8, 2008 at 16:57, Pierre Joye <[EMAIL PROTECTED]>
wrote:
On Mon, Dec 8, 2008 at 4:47 PM, Johannes Schlüter
<[EMAIL PROTECTED]> wrote:
When dropping magic_quotes the hosting company can do one of two
things:
a) not update to 5
Which reminds me that we still have no way to do that in userland.
In userland you cannot write:
function foo(Object $bla = NULL).
The missing part is 'Object' as a type hint. I once long ago suggested
using 'class' as in 'any class member'. But people felt it wouldn't be
self explanatory enough
Johannes Schlüter escribió:
> I don't safe stuff relying on magic_quotes is safe but kicking it will
> open up way more attack vectors... :-(
A false sense of security is worst than no security at all.
--
"We have art in order not to die of the truth" - Friedrich Nietzsche
Cristian Rodríguez
On 8 Dec 2008, at 16:35, Philip Olson <[EMAIL PROTECTED]> wrote:
On 8 Dec 2008, at 08:18, Hannes Magnusson wrote:
On Mon, Dec 8, 2008 at 16:57, Pierre Joye <[EMAIL PROTECTED]>
wrote:
On Mon, Dec 8, 2008 at 4:47 PM, Johannes Schlüter <[EMAIL PROTECTED]
net> wrote:
When dropping magic_quote
Hi Scott,
Agreed, going from on by default to removed just feels odd.
I'd disable it by default in 5.3 and lets start throwing a strict
error if the configuration enables it.
Why do we have E_DEPRECATED if we're not going to use it?
- Steph
--
PHP Internals - PHP Runtime Development M
Steph Fox wrote:
> Hi Scott,
>
>>> Agreed, going from on by default to removed just feels odd.
>
>> I'd disable it by default in 5.3 and lets start throwing a strict
>> error if the configuration enables it.
>
> Why do we have E_DEPRECATED if we're not going to use it?
That's the one I meant,
Hello Rodrigo,
Monday, December 8, 2008, 5:48:00 PM, you wrote:
>> Which reminds me that we still have no way to do that in userland.
>> In userland you cannot write:
>> function foo(Object $bla = NULL).
>> The missing part is 'Object' as a type hint. I once long ago suggested
>> using 'class'
Hi!
I am not speaking of a built-in object class. Because that is not what the
internal parsing does. The internal parsing checks whether a passed-in
Right now internal parser is quite detached from what PHP functions
could do. If someone would write a proposal to bring them closer
together
hi,
On Mon, Dec 8, 2008 at 5:53 PM, Scott MacVicar <[EMAIL PROTECTED]> wrote:
> I'd disable it by default in 5.3 and lets start throwing a strict error if
> the configuration enables it.
A fatal error could be more effective. And the message can make the
reason behind the error very clear.
By t
Pierre Joye wrote:
> hi,
>
> On Mon, Dec 8, 2008 at 5:53 PM, Scott MacVicar <[EMAIL PROTECTED]> wrote:
>
>> I'd disable it by default in 5.3 and lets start throwing a strict error if
>> the configuration enables it.
>
> A fatal error could be more effective. And the message can make the
> reason
Hi Pierre,
A fatal error could be more effective. And the message can make the
reason behind the error very clear.
It's a very big jump from 'enabled by default' to 'fatal error'. It will
break a lot of legacy code with no prior warning.
By the way and for the record here, they (magic quot
In my opinion a big change like droping something that was and still
used by many people are a "security measure", albeit a poor one is
something that can only be done in a major release.
On 8-Dec-08, at 10:47 AM, Johannes Schlüter wrote:
Hi,
let's take this to a new thread so it'S not h
On Mon, 8 Dec 2008, Ilia Alshanetsky wrote:
> In my opinion a big change like droping something that was and still used by
> many people are a "security measure", albeit a poor one is something that can
> only be done in a major release.
I concur.
regards,
Derick
--
HEAD before 5_3!: http://ti
On Mon, Dec 8, 2008 at 20:15, Derick Rethans <[EMAIL PROTECTED]> wrote:
> On Mon, 8 Dec 2008, Ilia Alshanetsky wrote:
>
>> In my opinion a big change like droping something that was and still used by
>> many people are a "security measure", albeit a poor one is something that can
>> only be done in
On Mon, Dec 8, 2008 at 8:38 PM, Hannes Magnusson <[EMAIL PROTECTED]> wrote:
> On Mon, Dec 8, 2008 at 20:15, Derick Rethans <[EMAIL PROTECTED]> wrote:
>> On Mon, 8 Dec 2008, Ilia Alshanetsky wrote:
>>
>>> In my opinion a big change like droping something that was and still used by
>>> many people ar
As much as I hate the feature, I am not certain that is a good idea in
a minor release.
On 8-Dec-08, at 2:38 PM, Hannes Magnusson wrote:
On Mon, Dec 8, 2008 at 20:15, Derick Rethans <[EMAIL PROTECTED]> wrote:
On Mon, 8 Dec 2008, Ilia Alshanetsky wrote:
In my opinion a big change like dropi
As much as I hate the feature, I am not certain that is a good idea in
a minor release.
"If not now, when?"
- Steph
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
6.0 iirc its already off by default in that branch.
On 8-Dec-08, at 3:12 PM, Steph Fox wrote:
As much as I hate the feature, I am not certain that is a good idea
in a minor release.
"If not now, when?"
- Steph
Ilia Alshanetsky
--
PHP Internals - PHP Runtime Development Mailing List
hi,
On Mon, Dec 8, 2008 at 9:48 PM, Ilia Alshanetsky <[EMAIL PROTECTED]> wrote:
> 6.0 iirc its already off by default in that branch.
It is not off by default, it has been removed completely. I re
introduced the check function (returning always false) later.
Cheers,
--
Pierre
http://blog.thepi
6.0 iirc its already off by default in that branch.
Ilia, it doesn't *exist* in that branch!
- Steph
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Hello Ilia,
given our current development model I completely agree. Thus I would like
to change it as described earlier. I am convinced that only following the
even=stable & odd=dev/testing model allows for longer maintenanance cycles
and fast development at the same time.
marcus
Monday, Decem
How would that model relate to patch, minor, major release schemes we
have right now. What you are proposing works for linux, where there is
only one "branch" and they can effectively do the odd/even approach.
But, what would it mean for PHP and our current versioning schema?
On 8-Dec-08,
On 08.12.2008, at 16:08, Pierre Joye wrote:
On Mon, Dec 8, 2008 at 4:06 PM, Hannes Magnusson
<[EMAIL PROTECTED]> wrote:
On Mon, Dec 8, 2008 at 15:24, Pierre Joye <[EMAIL PROTECTED]>
wrote:
hi,
On Mon, Dec 8, 2008 at 3:15 PM, Ilia Alshanetsky
<[EMAIL PROTECTED]> wrote:
Should the 5.3 relea
On 08.12.2008, at 16:08, Pierre Joye wrote:
On Mon, Dec 8, 2008 at 4:06 PM, Hannes Magnusson
<[EMAIL PROTECTED]> wrote:
On Mon, Dec 8, 2008 at 15:24, Pierre Joye <[EMAIL PROTECTED]>
wrote:
hi,
On Mon, Dec 8, 2008 at 3:15 PM, Ilia Alshanetsky
<[EMAIL PROTECTED]> wrote:
Should the 5.3 relea
On 08.12.2008, at 16:08, Pierre Joye wrote:
On Mon, Dec 8, 2008 at 4:06 PM, Hannes Magnusson
<[EMAIL PROTECTED]> wrote:
On Mon, Dec 8, 2008 at 15:24, Pierre Joye <[EMAIL PROTECTED]>
wrote:
hi,
On Mon, Dec 8, 2008 at 3:15 PM, Ilia Alshanetsky
<[EMAIL PROTECTED]> wrote:
Should the 5.3 relea
Mon, Dec 8, 2008 at 1:40 PM, Lukas Kahwe Smith <[EMAIL PROTECTED]> wrote:
> the drop was planned for 6.0 for a reason.
> i also do not think we need to make a 5.3 release just for this.
> lets focus on getting feedback on namespaces and the other changes and have
> this fixed on beta1 early 2009
On Tue, Dec 9, 2008 at 12:20 AM, mike <[EMAIL PROTECTED]> wrote:
> Mon, Dec 8, 2008 at 1:40 PM, Lukas Kahwe Smith <[EMAIL PROTECTED]> wrote:
>
>
>> the drop was planned for 6.0 for a reason.
>> i also do not think we need to make a 5.3 release just for this.
>> lets focus on getting feedback on na
The PHP development team would like to announce the immediate
availability of PHP 5.2.8. This release addresses a regression
introduced by 5.2.7 in regard to the magic_quotes functionality, that
was broken by an incorrect fix to the filter extension. All users who
have upgraded to 5.2.7 are
Hello,
I don't post here often, but I wanted to input my thoughts. For the
most part, I am a end user who developers PHP applications for mine
and others needs.
We can't just drop something so soon and expect others to catch up and
be able to operate with no problems at all. There is tons o
Hi!
"If not now, when?"
Later?
--
Stanislav Malyshev, Zend Software Architect
[EMAIL PROTECTED] http://www.zend.com/
(408)253-8829 MSN: [EMAIL PROTECTED]
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
"If not now, when?"
Later?
Would you mind reading the thread first please? :)
The subject's a tad misleading at this stage.
- Steph
--
Stanislav Malyshev, Zend Software Architect
[EMAIL PROTECTED] http://www.zend.com/
(408)253-8829 MSN: [EMAIL PROTECTED]
--
PHP Internals - PHP Runti
On Mon, Dec 8, 2008 at 22:40, Lukas Kahwe Smith <[EMAIL PROTECTED]> wrote:
>
> On 08.12.2008, at 16:08, Pierre Joye wrote:
>
>> On Mon, Dec 8, 2008 at 4:06 PM, Hannes Magnusson
>> <[EMAIL PROTECTED]> wrote:
>>>
>>> On Mon, Dec 8, 2008 at 15:24, Pierre Joye <[EMAIL PROTECTED]> wrote:
hi,
>
56 matches
Mail list logo
