Hi Ralph,
I don't have strong opinion about your suggestion.
In some cases this warning might help to find a typo, in others it may
be useless, but anyway, I think that usage of undefined class name is a
quite rare situation. I would prefer to keep it as is.
Thanks. Dmitry.
On 07/08/2011 06
Hi!
On 7/11/11 12:18 AM, Dmitry Stogov wrote:
Hi Ralph,
I don't have strong opinion about your suggestion.
In some cases this warning might help to find a typo, in others it may
be useless, but anyway, I think that usage of undefined class name is a
quite rare situation. I would prefer to keep
Hi Arnaud,
Is the main advantage of the patch - elimination of zval copy
constructor for IS_VAR and IS_CV operands?
Does it improve speed only for VAR/CV array operands?
Will the following script require an extra zval ealloc/efree with the patch?
For now the patch still looks a bit messing
Zitat von Ferenc Kovacs :
On Sun, Jul 10, 2011 at 11:17 PM, Pierre Joye wrote:
hi,
As I could agree on this fact, I can't find any existing project
having int(eger), float&co as class, namespaced or not. Do you have
any example at hand?
Cheers,
https://github.com/search?type=Code&languag
On Mon, Jul 11, 2011 at 09:25, Stas Malyshev wrote:
> Hi!
>
> On 7/11/11 12:18 AM, Dmitry Stogov wrote:
>>
>> Hi Ralph,
>>
>> I don't have strong opinion about your suggestion.
>>
>> In some cases this warning might help to find a typo, in others it may
>> be useless, but anyway, I think that usag
Hi!
That warning might be only emitted if the first operand is a name of non
existing class.
is_a("NonExistingClass", "MyClass");
I think you've missed my point. The point was people use this to check
if first argument is an instance of a certain class or something else -
and "something els
Hi Stas,
On 07/11/2011 11:25 AM, Stas Malyshev wrote:
Hi!
On 7/11/11 12:18 AM, Dmitry Stogov wrote:
Hi Ralph,
I don't have strong opinion about your suggestion.
In some cases this warning might help to find a typo, in others it may
be useless, but anyway, I think that usage of undefined clas
2011/7/10 Johannes Schlüter :
> Hi,
>
> On Wed, 2011-06-08 at 12:04 +0200, Johannes Schlüter wrote:
>>
>> Having the behavior cleared I wonder how useful it is in practical
>> terms. A class type hint guarantees me I can do a specific call to
>> methods defined in the class/interface. The proposed
Hi,
if somebody wonders why do we have those french guys registering on the wiki:
http://blog.mageekbox.net/?post/2011/07/10/La-r%C3%A9volution-est-en-marche-%21
the author thought that anybody can vote who has wiki account, but
that is corrected now.
however judging from the responses and the nu
On Mon, Jul 11, 2011 at 10:15 AM, Jan Schneider wrote:
>
> Zitat von Ferenc Kovacs :
>
>> On Sun, Jul 10, 2011 at 11:17 PM, Pierre Joye
>> wrote:
>>>
>>> hi,
>>>
>>> As I could agree on this fact, I can't find any existing project
>>> having int(eger), float&co as class, namespaced or not. Do you
Hi!
On 7/11/11 1:22 AM, Hannes Magnusson wrote:
Voting is open on this? I don't think I ever had the time to integrate
all the Q&A from this thread to the RFC.
If you think it's premature, we can postpone it. I've announced the
ballot on the list, but apparently not everybody is reading it ;)
On Mon, Jul 11, 2011 at 10:27, Stas Malyshev wrote:
> Hi!
>
> On 7/11/11 1:22 AM, Hannes Magnusson wrote:
>>
>> Voting is open on this? I don't think I ever had the time to integrate
>> all the Q&A from this thread to the RFC.
>
> If you think it's premature, we can postpone it. I've announced the
2011/7/11 Hannes Magnusson :
> 2011/7/10 Johannes Schlüter :
>> Hi,
>>
>> On Wed, 2011-06-08 at 12:04 +0200, Johannes Schlüter wrote:
>>>
>>> Having the behavior cleared I wonder how useful it is in practical
>>> terms. A class type hint guarantees me I can do a specific call to
>>> methods defined
Hello !
Hi,
if somebody wonders why do we have those french guys registering on the wiki:
http://blog.mageekbox.net/?post/2011/07/10/La-r%C3%A9volution-est-en-marche-%21
the author thought that anybody can vote who has wiki account, but
that is corrected now.
All my apologizes for this erro
Hi!
On 7/11/11 1:38 AM, Hannes Magnusson wrote:
I thought individual RFCs would be voted on first (into trunk), and
then there would be a vote on merging things from trunk.
This sort of heavy voting process is however new to me, will take some
time understanding and getting used to all the new r
Hi!
On 7/11/11 1:23 AM, Ferenc Kovacs wrote:
Hi,
if somebody wonders why do we have those french guys registering on the wiki:
http://blog.mageekbox.net/?post/2011/07/10/La-r%C3%A9volution-est-en-marche-%21
the author thought that anybody can vote who has wiki account, but
that is corrected no
Em Mon, 11 Jul 2011 00:47:50 +0100, Scott MacVicar
escreveu:
On Jul 10, 2011, at 4:46 PM, Stas Malyshev wrote:
On 7/10/11 4:23 PM, Scott MacVicar wrote:
The code for this looks really convoluted, I'm thinking we should
back out this multicast option for now. It's basically not going to
wor
OK. As I said I don't have strong opinion about this.
So fell free to remove the warning.
Thanks. Dmitry.
On 07/11/2011 12:18 PM, Stas Malyshev wrote:
Hi!
That warning might be only emitted if the first operand is a name of non
existing class.
is_a("NonExistingClass", "MyClass");
I think y
Hi
I'm a bit confused by the "Declare PHP/php as namespace reserved for
PHP internals" vote on https://wiki.php.net/todo/php54/vote
Why is there an option to select "PHP" or "php", and not just a yes/no question?
I'm even more confused by the people that voted only one or the other.
Namespaces a
On Mon, Jul 11, 2011 at 11:38 AM, Hannes Magnusson
wrote:
> Hi
>
> I'm a bit confused by the "Declare PHP/php as namespace reserved for
> PHP internals" vote on https://wiki.php.net/todo/php54/vote
>
> Why is there an option to select "PHP" or "php", and not just a yes/no
> question?
>
> I'm even
hi,
On Mon, Jul 11, 2011 at 10:45 AM, Stas Malyshev wrote:
> I'd say for core features everybody with write access to the core, but then
> again,
Everyone with @php.net is what was decided.
> not sure about how to formalize that. Note that vote isn't meant to
> be the decision. At least I thin
On 11 July 2011 17:43, Pierre Joye wrote:
> On Mon, Jul 11, 2011 at 10:45 AM, Stas Malyshev
> wrote:
> > I'd say for core features everybody with write access to the core, but then
> > again,
>
> Everyone with @php.net is what was decided.
Was it? The RFC wasn't exactly clear on that one: the w
On Mon, Jul 11, 2011 at 11:47 AM, Adam Harvey wrote:
> On 11 July 2011 17:43, Pierre Joye wrote:
>> On Mon, Jul 11, 2011 at 10:45 AM, Stas Malyshev
>> wrote:
>> > I'd say for core features everybody with write access to the core, but then
>> > again,
>>
>> Everyone with @php.net is what was dec
On Mon, Jul 11, 2011 at 10:45, Stas Malyshev wrote:
> Hi!
>
> On 7/11/11 1:23 AM, Ferenc Kovacs wrote:
>>
>> Hi,
>>
>> if somebody wonders why do we have those french guys registering on the
>> wiki:
>>
>> http://blog.mageekbox.net/?post/2011/07/10/La-r%C3%A9volution-est-en-marche-%21
>>
>> the au
On Mon, Jul 11, 2011 at 11:53 AM, Hannes Magnusson
wrote:
> On Mon, Jul 11, 2011 at 10:45, Stas Malyshev wrote:
>> Hi!
>>
>> On 7/11/11 1:23 AM, Ferenc Kovacs wrote:
>>>
>>> Hi,
>>>
>>> if somebody wonders why do we have those french guys registering on the
>>> wiki:
>>>
>>> http://blog.mageekbox
about the fix, instead of "only registered users", we have to add
group support, so we can add php-src/doc/etc. to it and manually add
external and approved persons. If anyone has time to do it, please go
ahead, code is in SVN.
On Mon, Jul 11, 2011 at 11:56 AM, Pierre Joye wrote:
> On Mon, Jul 11
On Mon, Jul 11, 2011 at 11:56, Pierre Joye wrote:
> On Mon, Jul 11, 2011 at 11:53 AM, Hannes Magnusson
> wrote:
>> On Mon, Jul 11, 2011 at 10:45, Stas Malyshev wrote:
>>> Hi!
>>>
>>> On 7/11/11 1:23 AM, Ferenc Kovacs wrote:
Hi,
if somebody wonders why do we have those french
On Mon, Jul 11, 2011 at 11:59 AM, Hannes Magnusson
wrote:
> There is no "accept an account". Thanks.
>
> Creating an account in the wiki, creates an account.
> Like I said, the user doesn't have write access to anything unless
> someone explicitly gives him write access (usually to /rfc, or /web)
It is very hard to detect which "php group" a person belongs to, our
karma system doesn't work like that.
We can easily detect if an account is an php.net SVN account though.
And the wiki can tell you if a person has write access to that specific page.
Most external users have assigned "write" gr
On Mon, Jul 11, 2011 at 12:03 PM, Hannes Magnusson
wrote:
> It is very hard to detect which "php group" a person belongs to, our
> karma system doesn't work like that.
>
> We can easily detect if an account is an php.net SVN account though.
> And the wiki can tell you if a person has write access
hi,
On Mon, Jul 11, 2011 at 12:03 PM, Hannes Magnusson
wrote:
> It is very hard to detect which "php group" a person belongs to, our
> karma system doesn't work like that.
It is somehow easier in the wiki, we have groups afair. Also for the
votes, only svn account is enough, and "vote" group for
On Mon, Jul 11, 2011 at 12:03, Hannes Magnusson
wrote:
> It is very hard to detect which "php group" a person belongs to, our
> karma system doesn't work like that.
>
> We can easily detect if an account is an php.net SVN account though.
> And the wiki can tell you if a person has write access to
On Mon, Jul 11, 2011 at 12:07 PM, Hannes Magnusson
wrote:
> On Mon, Jul 11, 2011 at 12:03, Hannes Magnusson
> wrote:
>> It is very hard to detect which "php group" a person belongs to, our
>> karma system doesn't work like that.
>>
>> We can easily detect if an account is an php.net SVN account t
Hi Dmitry,
Le Monday 11 July 2011 09:49:27, Dmitry Stogov a écrit :
> Hi Arnaud,
>
> Is the main advantage of the patch - elimination of zval copy
> constructor for IS_VAR and IS_CV operands?
Yes.
Currently the ternary operator does a copy of its second and third operands.
This is costly when
For now the patch still looks a bit messing to me. Also, I would
probably prefer to use new opcodes ZEND_QM_ASSIGN_VAR and ZEND_JMP_SET_VAR.
Ok, I'll change the patch to use new opcodes instead
It's not necessary yet.
Please, let me think a bit more.
Thanks. Dmitry.
--
PHP Internals - PH
On 11 July 2011 09:26, Pierre Joye wrote:
> On Mon, Jul 11, 2011 at 10:15 AM, Jan Schneider wrote:
>> Try that for String and it reveals a different picture. Horde 3 used that
>> too FWIW.
>>
>> Jan.
>
> Even the php5 versions of Horde? That's rather bad given the so strong
> and loud warnings we
On Mon, Jul 11, 2011 at 12:18 PM, Ferenc Kovacs wrote:
> On Mon, Jul 11, 2011 at 12:07 PM, Hannes Magnusson
> wrote:
>> On Mon, Jul 11, 2011 at 12:03, Hannes Magnusson
>> wrote:
>>> It is very hard to detect which "php group" a person belongs to, our
>>> karma system doesn't work like that.
>>>
On Mon, Jul 11, 2011 at 12:48, Ferenc Kovacs wrote:
> On Mon, Jul 11, 2011 at 12:18 PM, Ferenc Kovacs wrote:
>> On Mon, Jul 11, 2011 at 12:07 PM, Hannes Magnusson
>> wrote:
>>> On Mon, Jul 11, 2011 at 12:03, Hannes Magnusson
>>> wrote:
It is very hard to detect which "php group" a person b
On Sun, Jul 3, 2011 at 4:15 PM, Felipe Pena wrote:
> I like the idea (and voted +1 on it), but I've some consideration to do:
>
> +/* {{{ proto bool SessionHandler::open(string save_path, string session_name)
> + Wraps the old open handler */
> +PHP_METHOD(SessionHandler, open)
> +{
> + PS
Hiya,
I've been playing with the built-in server, and have some concerns over how
static assets are handled.
Currently, to run an application on the built-in server, we essentially need
to list out all the static assets that should be served directly from disk.
This is the opposite of what I beli
Hey Kiall,
An optional argument to the built in web server can be a php based
router. If the router returns false, it will attempt to return the
resource as-it-is on disk.
Your command line looks like this:
php -S localhost:8000 -t ./path/to/docroot routing.php
routing.php can be one of tw
On 2011-07-10, Philip Olson wrote:
> Greetings PHP geeks,
>
> Don't panic! This is not a proposal to add errors or remove this
> popular extension. Not yet anyway, because it's too popular to do that
> now.
>
> The documentation team is discussing the database security situation,
> and educating u
Hi Ralph,
I'm aware of the ability to use a routing script to determine which files to
serve via a "return false;".
My concern is that every framework / application etc is going to need one in
order to work with the built-in server (even if they all need the same
one!)..
So considering this func
On 11 July 2011 01:03, Philip Olson wrote:
> What this means to ext/mysql:
>
> - Softly deprecate ext/mysql with education (docs) starting today
> - Not adding E_DEPRECATED errors in 5.4, but revisit for 5.5/6.0
> - Add pdo_mysql examples within the ext/mysql docs that mimic the current
> exa
On 2011-07-10, Stas Malyshev wrote:
> On 7/10/11 9:41 AM, Patrick ALLAERT wrote:
> > Developer may have taken care of defining them in a specific
> > namespace, would it be possible to not break their application while
> > making them reserved keywords in the global namespace only?
>
> I don't thi
it does seem silly that the server would even try to serve those files
rather than check if they are of a certain header/mime before, but at least
with this method it does mean that you can "fix" your code to always bypass
this, and if your purposlly testing through the CLI-server anyway, changing
On Mon, Jul 11, 2011 at 1:00 PM, Hannes Magnusson
wrote:
> On Mon, Jul 11, 2011 at 12:48, Ferenc Kovacs wrote:
>> On Mon, Jul 11, 2011 at 12:18 PM, Ferenc Kovacs wrote:
>>> On Mon, Jul 11, 2011 at 12:07 PM, Hannes Magnusson
>>> wrote:
On Mon, Jul 11, 2011 at 12:03, Hannes Magnusson
w
maybe we should get another E_, E_NEARLY_DEPRECATED that way we can set this
to that, and then 5.5 we can move it to E_DEPRECATED, that way people have
to go read the docs, the amount of people even those who have been in the
field for years, that dont know about php.net/ and still look stuff up
on
On Mon, Jul 11, 2011 at 5:08 PM, Matthew Weier O'Phinney
wrote:
> On 2011-07-10, Stas Malyshev wrote:
>> On 7/10/11 9:41 AM, Patrick ALLAERT wrote:
>> > Developer may have taken care of defining them in a specific
>> > namespace, would it be possible to not break their application while
>> > maki
On 7/10/11 10:03 AM, Philip Olson wrote:
What this means to ext/mysql:
- Softly deprecate ext/mysql with education (docs) starting today
- Not adding E_DEPRECATED errors in 5.4, but revisit for 5.5/6.0
- Add pdo_mysql examples within the ext/mysql docs that mimic the current
example
On Mon, Jul 11, 2011 at 4:41 PM, Christopher Jones
wrote:
>
>
> On 7/10/11 10:03 AM, Philip Olson wrote:
>
>> What this means to ext/mysql:
>>
>> - Softly deprecate ext/mysql with education (docs) starting today
>> - Not adding E_DEPRECATED errors in 5.4, but revisit for 5.5/6.0
>> - Add pdo_my
On Jul 11, 2011, at 8:11 AM, Ferenc Kovacs wrote:
> On Mon, Jul 11, 2011 at 1:00 PM, Hannes Magnusson
> wrote:
>> On Mon, Jul 11, 2011 at 12:48, Ferenc Kovacs wrote:
>>> On Mon, Jul 11, 2011 at 12:18 PM, Ferenc Kovacs wrote:
On Mon, Jul 11, 2011 at 12:07 PM, Hannes Magnusson
wrote:
I'm an SDET at Microsoft, working with Pierre Joye and will primarily be
submitting additional test cases.
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
On 2011-07-11, Paul Dragoonis wrote:
> On Mon, Jul 11, 2011 at 4:41 PM, Christopher Jones
> wrote:
> > On 7/10/11 10:03 AM, Philip Olson wrote:
> > > What this means to ext/mysql:
> > >
> > > - Softly deprecate ext/mysql with education (docs) starting today
> > > - Not adding E_DEPRECATED error
On Mon, Jul 11, 2011 at 19:05, Philip Olson wrote:
>
> On Jul 11, 2011, at 8:11 AM, Ferenc Kovacs wrote:
>
>> On Mon, Jul 11, 2011 at 1:00 PM, Hannes Magnusson
>> wrote:
>>> On Mon, Jul 11, 2011 at 12:48, Ferenc Kovacs wrote:
On Mon, Jul 11, 2011 at 12:18 PM, Ferenc Kovacs wrote:
> On
On July-11-11 Matthew Weier O'Phinney wrote:
> Sent: July-11-11 1:57 PM
> To: internals@lists.php.net
> Subject: Re: [PHP-DEV] deprecating ext/mysql
>
> On 2011-07-11, Paul Dragoonis
> >
> > Yes, +1 from me too. I do indeed think we need to make this a smooth
> > transition over time. Possibly t
Hi!
On 7/11/11 11:24 AM, Hannes Magnusson wrote:
The current vote still needs to be reviewed manually anyway, so I
really don't understand the need for a quick hack at this time.
Cooperating with the plugin authors on how to implement better checks
there would imo make much more sense.
Is ther
On 11 July 2011 20:07, Stas Malyshev wrote:
> Hi!
>
> On 7/11/11 11:24 AM, Hannes Magnusson wrote:
>>
>> The current vote still needs to be reviewed manually anyway, so I
>> really don't understand the need for a quick hack at this time.
>> Cooperating with the plugin authors on how to implement b
On Mon, Jul 11, 2011 at 9:23 PM, Peter Cowburn wrote:
> On 11 July 2011 20:07, Stas Malyshev wrote:
>> Hi!
>>
>> On 7/11/11 11:24 AM, Hannes Magnusson wrote:
>>>
>>> The current vote still needs to be reviewed manually anyway, so I
>>> really don't understand the need for a quick hack at this tim
On Mon, Jul 11, 2011 at 21:38, Ferenc Kovacs wrote:
> On Mon, Jul 11, 2011 at 9:23 PM, Peter Cowburn wrote:
>> On 11 July 2011 20:07, Stas Malyshev wrote:
>>> Hi!
>>>
>>> On 7/11/11 11:24 AM, Hannes Magnusson wrote:
The current vote still needs to be reviewed manually anyway, so I
> Stas means when we print who has voted, to only print votes by people
> in that group so you won't need to manually filter out
> not-allowed-to-vote votes.
>
> -Hannes
>
I see.
if you only need the @php.net usernames, you can use the
https://master.php.net/fetch/allusers.php api with the proper
2011/7/11 Ferenc Kovacs :
> On Mon, Jul 11, 2011 at 5:08 PM, Matthew Weier O'Phinney
[snip]
>> I think that's a bad idea. The point of namespaces is to allow us to
>> override classes (and functions, and constants) within that namespace.
>> If I can't do this:
>>
>> namespace Foo
>> {
>>
On Mon, Jul 11, 2011 at 22:13, Ferenc Kovacs wrote:
>> Stas means when we print who has voted, to only print votes by people
>> in that group so you won't need to manually filter out
>> not-allowed-to-vote votes.
>>
>> -Hannes
>>
>
> I see.
> if you only need the @php.net usernames, you can use th
On Mon, Jul 11, 2011 at 11:09 PM, Hannes Magnusson
wrote:
> On Mon, Jul 11, 2011 at 22:13, Ferenc Kovacs wrote:
>>> Stas means when we print who has voted, to only print votes by people
>>> in that group so you won't need to manually filter out
>>> not-allowed-to-vote votes.
>>>
>>> -Hannes
>>>
>
On 08/07/11 17:28, Richard Quadling wrote:
On 8 July 2011 17:21, DIXON P. wrote:
Thanks Richard,
Renamed and attached.
-Original Message-
From: Richard Quadling [mailto:rquadl...@gmail.com]
Sent: 08 July 2011 17:13
To: DIXON P.
Cc: internals@lists.php.net
Subject: Re: [PHP-DEV] [PATCH
On Mon, Jul 11, 2011 at 23:23, Ferenc Kovacs wrote:
> On Mon, Jul 11, 2011 at 11:09 PM, Hannes Magnusson
> wrote:
>> On Mon, Jul 11, 2011 at 22:13, Ferenc Kovacs wrote:
Stas means when we print who has voted, to only print votes by people
in that group so you won't need to manually fil
Hi!
On 7/11/11 3:20 PM, Hannes Magnusson wrote:
The idea Stas proposed of leaving the votes untouched and just hide
those specific votes during rendering of the vote results is very
silly to me.
Manually summerizing the votes like has been done in the past on many
RFCs into "with karma" and "wit
On Tue, Jul 12, 2011 at 00:34, Stas Malyshev wrote:
> Hi!
>
> On 7/11/11 3:20 PM, Hannes Magnusson wrote:
>>
>> The idea Stas proposed of leaving the votes untouched and just hide
>> those specific votes during rendering of the vote results is very
>> silly to me.
>> Manually summerizing the votes
Hi!
I'm planning to do 5.4 alpha 2 on 14th (Thursday this week), so if
anybody has anything urgent for it or any comments/requests, please talk
to me ASAP.
--
Stanislav Malyshev, Software Architect
SugarCRM: http://www.sugarcrm.com/
(408)454-6900 ext. 227
--
PHP Internals - PHP Runtime Develo
hi,
I would rather wait the 2nd wave of RFCs to be adopted/rejected before
doing a2, if some has no patch (or far to be ready) or too risky (the
int/string/float looks like one to me) should be dropped and delayed
to the next release.
On Tue, Jul 12, 2011 at 12:53 AM, Stas Malyshev wrote:
> Hi!
Hi
2011/7/12 Pierre Joye :
> hi,
>
> I would rather wait the 2nd wave of RFCs to be adopted/rejected before
> doing a2, if some has no patch (or far to be ready) or too risky (the
> int/string/float looks like one to me) should be dropped and delayed
> to the next release.
I agree, it would make
hi Hannes,
On Mon, Jul 11, 2011 at 11:09 PM, Hannes Magnusson
wrote:
> On Mon, Jul 11, 2011 at 22:13, Ferenc Kovacs wrote:
>>> Stas means when we print who has voted, to only print votes by people
>>> in that group so you won't need to manually filter out
>>> not-allowed-to-vote votes.
>>>
>>> -
Hi!
On 7/11/11 4:16 PM, Pierre Joye wrote:
I would rather wait the 2nd wave of RFCs to be adopted/rejected before
doing a2, if some has no patch (or far to be ready) or too risky (the
int/string/float looks like one to me) should be dropped and delayed
to the next release.
Why delay? RFCs are
On Jul 11, 2011, at 3:48 PM, Hannes Magnusson wrote:
> On Tue, Jul 12, 2011 at 00:34, Stas Malyshev wrote:
>> Hi!
>>
>> On 7/11/11 3:20 PM, Hannes Magnusson wrote:
>>>
>>> The idea Stas proposed of leaving the votes untouched and just hide
>>> those specific votes during rendering of the vote
On Tue, Jul 12, 2011 at 1:23 AM, Stas Malyshev wrote:
> Hi!
>
> On 7/11/11 4:16 PM, Pierre Joye wrote:
>>
>> I would rather wait the 2nd wave of RFCs to be adopted/rejected before
>> doing a2, if some has no patch (or far to be ready) or too risky (the
>> int/string/float looks like one to me) sho
Hi!
On 7/11/11 4:20 PM, Kalle Sommer Nielsen wrote:
I agree, it would make more sense to have the votings over before
doing the next Alpha, so theres time to cook up relevant patches and
commit them.
Well, OK, let's say we delay a week. Vote closes on 16th, and I'd have
to pack on 20th, so we
Hi!
On 7/11/11 4:24 PM, Philip Olson wrote:
The patch fixed a bug where the voting mechanism was not in sync with the
passed voting RFC. It's closer now to most peoples interpretation of said
RFC. Changing this would, I'm afraid, require changing the RFC which I
suppose means an amendment [with
On Jul 8, 2011, at 11:30 PM, Stas Malyshev wrote:
> Hi!
>
> I've created a voting page for the features in 5.4 TODO list for which we
> need to find consensus. Please go there:
> https://wiki.php.net/todo/php54/vote
> and vote!
>
> See also links to relevant RFCs on the TODO page:
> https://w
Hi!
On 7/11/11 5:09 PM, Philip Olson wrote:
this previously accepted RFC is not about removing magic quotes. And I'm the
author of said RFC. It deals with PHP 5.3 which removed get_magic_quotes_*()
so this old RFC restored them into both PHP 5.3+ and PHP 6.
Yes, it's not exactly what is being
79 matches
Mail list logo
