Am 07.06.2011 04:42, schrieb Martin Scotta:
> On Mon, Jun 6, 2011 at 8:15 PM, Reindl Harald wrote:
>
>>
>> Am 06.06.2011 23:40, schrieb Martin Scotta:
>>
>>> It'd be very nice if some extension could be enabled just by dropping the
>>> "extension file" on the path.
>>> So developers can check wh
Rasmus wrote:
On 06/06/2011 08:38 PM, Lester Caine wrote:
Stas Malyshev wrote:
For many of us, the 5.2 branch HAS been the 'long term stability'
version of PHP
Any version beyond it's support period would be "long term stability"
(as in "pining for the fjords" stability) by definition. If som
Martin Scotta wrote:
It'd be very nice if some extension could be enabled just by dropping the
"extension file" on the path.
So developers can check what they have using phpinfo, and then upload the
needed extension using ftp. Is it possible?
if a "developer" only would try such idiotic action
Martin Scotta
On Mon, Jun 6, 2011 at 8:02 PM, Stas Malyshev wrote:
> Hi!
>
>
> The point, though, is that with such a typehint available, we can reduce
>> boilerplate code like the following:
>>
>
> Sure. How about reducing boilterplate code like this:
>
> if(is_readable($foo)) {
> $var = fil
Martin Scotta
On Mon, Jun 6, 2011 at 8:15 PM, Reindl Harald wrote:
>
> Am 06.06.2011 23:40, schrieb Martin Scotta:
>
> > It'd be very nice if some extension could be enabled just by dropping the
> > "extension file" on the path.
> > So developers can check what they have using phpinfo, and then
On 07/06/11 01:49, Stas Malyshev wrote:
> Hi!
>
>> Currently off the shelf, 5.2.17 is the 'old stable' but for some
>> windows users
>> it IS the only available version. Changing the rest of the
>> infrastructure to
>
> 5.2.17 is unsupported. It is announced on php.net. Now, some Windows
> users, d
On 06/06/2011 08:38 PM, Lester Caine wrote:
> Stas Malyshev wrote:
>>> For many of us, the 5.2 branch HAS been the 'long term stability'
>>> version of PHP
>>
>> Any version beyond it's support period would be "long term stability"
>> (as in "pining for the fjords" stability) by definition. If some
Stas Malyshev wrote:
For many of us, the 5.2 branch HAS been the 'long term stability'
version of PHP
Any version beyond it's support period would be "long term stability"
(as in "pining for the fjords" stability) by definition. If somebody
want to backport patches and provide builds for it for
On Mon, 6 Jun 2011, Matthew Weier O'Phinney wrote:
> The point, though, is that with such a typehint available, we can
> reduce boilerplate code like the following:
>
> public function addCallback($callback)
> {
> if (!is_callback($callback)) {
> throw new InvalidArgu
Hi Stas,
On Mon, Jun 6, 2011 at 4:02 PM, Stas Malyshev wrote:
>
> I wouldn't love it a bit, frankly, as "rely on PHP's native error handling"
> in this context means "bombing out in runtime without any idea what went
> wrong". When you have exception, you could make it print what happened and
> r
On 06/05/2011 03:27 PM, Stas Malyshev wrote:
This is a prime example of what we're talking about. Several have
expressed a desire to follow an Ubuntu style of branching instead
of the style proposed in said RFC. This is a core issue, so the
RFC is certainly not ready to adopt.
So does this re
Am 06.06.2011 23:40, schrieb Martin Scotta:
> It'd be very nice if some extension could be enabled just by dropping the
> "extension file" on the path.
> So developers can check what they have using phpinfo, and then upload the
> needed extension using ftp. Is it possible?
if a "developer" only
Martin Scotta wrote:
It'd be very nice if some extension could be enabled just by dropping the
"extension file" on the path.
So developers can check what they have using phpinfo, and then upload the
needed extension using ftp. Is it possible?
This depends on what distribution you are using in L
Hi!
For many of us, the 5.2 branch HAS been the 'long term stability' version of PHP
Any version beyond it's support period would be "long term stability"
(as in "pining for the fjords" stability) by definition. If somebody
want to backport patches and provide builds for it for any period he
Hi!
The point, though, is that with such a typehint available, we can reduce
boilerplate code like the following:
Sure. How about reducing boilterplate code like this:
if(is_readable($foo)) {
$var = file_get_contents($foo);
} else {
throw InvalidArgumentException();
}
Why won't we make
On Mon, 2011-06-06 at 18:40 -0300, Martin Scotta wrote:
> It'd be very nice if some extension could be enabled just by dropping the
> "extension file" on the path.
> So developers can check what they have using phpinfo, and then upload the
> needed extension using ftp. Is it possible?
No sane sysa
On Mon, Jun 6, 2011 at 9:41 PM, Hannes Magnusson wrote:
> Hi
>
> As quickly mentioned in the '$arr = array('Hello', 'world'); $arr();'
> thread[1], we are hitting the need for a callable typehint.
>
>
> See attached patch+phpt; Any objections to include it in 5.4?
>
> -Hannes
>
> [1] http://php.m
On Mon, 2011-06-06 at 22:30 +0200, Mike van Riel wrote:
> 1. Does it hurt to disable the Zend MM?
> 2. Can it be done from inside a PHP Script?
> 3. Why is the memory consumption so much lower, even lower than my
> calculations?
When you disable Zend MM PHP will not use it but directly the system
Stas Malyshev wrote:
Hi!
The reason for the connection is simple ... currently PHP5.2 IS the
LTS version
for MANY users who are running windows based apache servers. Which is
the only
If that's what you mean by LTS, then discussing it is meaningless, as
nothing here depends on us - the users
On Mon, 2011-06-06 at 12:53 -0400, Matthew Weier O'Phinney wrote:
> > But one thing is sure, all distributions do include mongodb,
> > memcache(d), couchdb, etc. If you can't run an apt-get install
> > memcached (non core), just like you run apt-get install pdo_mysql
> > (core), then there is somet
On Mon, Jun 6, 2011 at 11:40 PM, Martin Scotta wrote:
> Martin Scotta
>
>
> On Mon, Jun 6, 2011 at 2:01 PM, Pierre Joye wrote:
>
> > On Mon, Jun 6, 2011 at 6:53 PM, Matthew Weier O'Phinney
> > wrote:
> >
> > > My point is that perhaps PHP has missed the boat a bit by moving
> > > everything int
Hello,
On Mon, Jun 6, 2011 at 3:51 PM, Chris Stockton
wrote:
> Hello,
>
> On Mon, Jun 6, 2011 at 12:41 PM, Hannes Magnusson
> wrote:
>> Hi
>>
>> As quickly mentioned in the '$arr = array('Hello', 'world'); $arr();'
>> thread[1], we are hitting the need for a callable typehint.
>>
>
> This brings
Hello,
On Mon, Jun 6, 2011 at 12:41 PM, Hannes Magnusson
wrote:
> Hi
>
> As quickly mentioned in the '$arr = array('Hello', 'world'); $arr();'
> thread[1], we are hitting the need for a callable typehint.
>
This brings a clear and concise enhancement to PHP which I would
benefit from .I have bee
Hi!
The reason for the connection is simple ... currently PHP5.2 IS the LTS version
for MANY users who are running windows based apache servers. Which is the only
If that's what you mean by LTS, then discussing it is meaningless, as
nothing here depends on us - the users will do it regardless
Hi!
Ok, I've committed in 5.4 and trunk the argument parser part.
Now I need to fix some tests and try to found other places needing for
related checks.
Thanks for fixing it!
--
Stanislav Malyshev, Software Architect
SugarCRM: http://www.sugarcrm.com/
(408)454-6900 ext. 227
--
PHP Internals
Stas Malyshev wrote:
As much as I appreciate everybody taking this opportunity to vent about
their troubles with Apache on Windows, could we not hijack this topic -
which was about release management and in particular LTS - and turn it
into Apache on Windows topic? We can have separate Apache on
Hi,
On Mon, Jun 6, 2011 at 22:35, Stas Malyshev wrote:
> Hi!
>
>> See attached patch+phpt; Any objections to include it in 5.4?
>
> Yes, same objections as for other static typing.
Those objections do not apply here IMO.
IIRC, the main objections were that if we introduce strict hints for
scala
On 2011-06-06, Pierre Joye wrote:
> --0016e6de0029ddc06f04a5129914
> Content-Type: text/plain; charset=ISO-8859-1
>
> How is this argument different than the one in favor of type hinting (or
> whatever was what ended in trunk)?
I was simply voicing my support for Hannes' patch, and trying to cla
How is this argument different than the one in favor of type hinting (or
whatever was what ended in trunk)?
On 7 Jun 2011 00:16, "Matthew Weier O'Phinney"
wrote:
> On 2011-06-06, Stas Malyshev wrote:
>> > Like I mentioned in the other thread (which I probably should had
>> > repeated here), a l
On 2011-06-06, Chad Fulton wrote:
> So, I would advocate a "white list" of core devs for formal voting (of
> which, for example, I would not be a member). I think this mailing
> list has grown sufficiently that "public opinion" can be gauged from
> here: everyone can write their opinion without gi
On 2011-06-06, Stas Malyshev wrote:
> > Like I mentioned in the other thread (which I probably should had
> > repeated here), a lot of libs/frameworks are using the 'Closure'
> > typehint for callbacks.
>
> Well, they are wrong (unless they mean to use only closures and not
> callbacks). But that'
Hi,
2011/6/5 Stas Malyshev
> Hi!
>
>
> Of course, I was just checking if it's what you guys are thinking first.
>>
>
> Well, there was basically two ideas:
> 1. Add filename length to streams and check inside streams
> 2. Check inside argument parser
>
> Both have downsides: (1) does not captur
Martin Scotta
On Mon, Jun 6, 2011 at 3:03 PM, Matthew Weier O'Phinney <
weierophin...@php.net> wrote:
> On 2011-06-01, Sean Coates wrote:
> > > Now, the only reason I would personally support the array shortcut is
> > > if it was an implementation of JSON. I know that's not on the table
> > >
Hi,
2011/6/6 Dmitry Stogov
> Hi Felipe,
>
> I like the idea. It makes indirect method calls less expensive.
>
> I would add a hint to specializer, to eliminate small overhead for regular
> function calls.
>
> } else if (OP1_TYPE != IS_CONST &&
> EXPECTED(Z_TYPE_P(function_name) == IS_A
Martin Scotta
On Mon, Jun 6, 2011 at 2:01 PM, Pierre Joye wrote:
> On Mon, Jun 6, 2011 at 6:53 PM, Matthew Weier O'Phinney
> wrote:
>
> > My point is that perhaps PHP has missed the boat a bit by moving
> > everything into extensions. Perhaps if an extension is particularly
> > popular, it sh
On Mon, Jun 6, 2011 at 12:27 PM, dukeofgaming wrote:
>
> I have a little proposition here.
>
> I'm not —at least currently— known for any app or framework, but I'd like my
> voice to count, that is, if and only if the rest of the community thinks I
> make sane arguments that are worth considering.
Hi!
Like I mentioned in the other thread (which I probably should had
repeated here), a lot of libs/frameworks are using the 'Closure'
typehint for callbacks.
Well, they are wrong (unless they mean to use only closures and not
callbacks). But that's no reason to do wrong thing in the language
On 06/05/2011 08:52 AM, Felipe Pena wrote:
Hi all,
Reading our bug tracker I noticed a good feature request [1] from 2009 which
points to an interesting feature that I think makes sense for us, since we
are now working with $f() using objects and strings, and the array('class',
'method') is an
On 06/06/2011 12:41 PM, Hannes Magnusson wrote:
See attached patch+phpt; Any objections to include it in 5.4?
Hannes,
How about putting up an RFC for it? Even a brief RFC would be better than none.
Chris
--
Email: christopher.jo...@oracle.com
Tel: +1 650 506 8630
Blog: http://blogs.ora
On Mon, Jun 6, 2011 at 22:35, Stas Malyshev wrote:
> Hi!
>
>> See attached patch+phpt; Any objections to include it in 5.4?
>
> Yes, same objections as for other static typing.
>
That was totally not the purpose of this, and I don't quite understand
how you made the connection.
Like I mentioned
Hi!
A PHP developers view on windows installation: it's screwed as hell right
now. I use apache + php for my developing envoirment on Windows 7. Guys - I
spend 1.5, freaking 1.5 hours setting up apache + php!!! essentially i just
As much as I appreciate everybody taking this opportunity to ven
Hi!
See attached patch+phpt; Any objections to include it in 5.4?
Yes, same objections as for other static typing.
--
Stanislav Malyshev, Software Architect
SugarCRM: http://www.sugarcrm.com/
(408)454-6900 ext. 227
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit
David and Pauli,
When I change the test script to:
var_dump(memory_get_peak_usage());
gc_collect_cycles();
token_get_all(file_get_contents());
gc_collect_cycles();
var_dump(memory_get_peak_usage());
And execute the following bash line preceding:
export USE_ZEND_ALLOC=0
>>> $foo = {
>>> 'bar' : function(){
>>> echo 'baz';
>>> }
>>> };
>>>
>>> $foo->bar();
>>
>> I guess it's not yet too late to surpass Perl in the front of obscurity...
>
> Since the stuff to the right of the assignment operator (`:` in this case) is
> valid PHP, I don't see why this wo
Hi
As quickly mentioned in the '$arr = array('Hello', 'world'); $arr();'
thread[1], we are hitting the need for a callable typehint.
See attached patch+phpt; Any objections to include it in 5.4?
-Hannes
[1] http://php.markmail.org/message/gdas65h3im52sleg
Index: Zend/zend.h
===
On Sun, Jun 5, 2011 at 5:20 PM, Pierre Joye wrote:
>
>
> I'd to go with a 60% for language syntax, 50+1 for new exts or sapis.
> Other question is who can vote. For one, I like to have external
> people being able to vote, like frameworks/apps lead developers as
> well as @php.net in general (docs
Hello.
A PHP developers view on windows installation: it's screwed as hell right
now. I use apache + php for my developing envoirment on Windows 7. Guys - I
spend 1.5, freaking 1.5 hours setting up apache + php!!! essentially i just
had to download and try multiple binaries for windows to find the
On 06/06/2011 01:48 AM, Tom Samplonius wrote:
So RHEL6 will have whatever PHP that was around, then, which I
hope is PHP 5.3 (I don't have any RHEL6 servers yet). So RHEL6
will always be PHP5.3.x based.
RHEL 6.0's php-* packages are PHP 5.3.2. RHEL 6.1's uses PHP 5.3.3.
RHEL 5.6 h
Hi!
Media Temple's Grid servers still default to PHP 4.4.9. With the option of
using 5.2.16, but you have to explicitly tell it to use that version in your
.htaccess file.
This is pretty bad, but LTS would only make this problem worse - imagine
if 4.4 were LTS, they'd say "oh, we are install
Pierre Joye wrote:
However I ask you, strongly, now to stop to pollute this thread with
totally unrelated topics. Thanks for your understanding.
This is something of a rather important point since PHP has always been very
strongly related to Apache so it is totally related to a discussion of m
On Mon, Jun 6, 2011 at 8:11 PM, Lester Caine wrote:
> PERHAPS such important information could be made available to REAL USERS?
> There has never been any public statement to that effect!
For the 10th time, please stop to uppercase every 2nd word.
> Until you came on the scene I had never even
Media Temple's Grid servers still default to PHP 4.4.9. With the option of
using 5.2.16, but you have to explicitly tell it to use that version in your
.htaccess file.
On Mon, Jun 6, 2011 at 2:03 PM, John Crenshaw wrote:
>
> From: David Muir [mailto:davidkm...@gmail.com]
>
> On 06/06/11 17:48, T
Pierre Joye wrote:
> Please can you provide a link where THAT statement is made!
Chech the php windows internals list archive as well as the httpd
devel ones. This statement has been written numerous times in both
lists.
PERHAPS such important information could be made available to REAL USERS
On 06.06.2011, at 20:03, John Crenshaw wrote:
> The desire is to be able to copy/paste things back and forth and make it work
> with only minor tweaks.
That sounds like a problem an IDE should solve, and not the language itself.
And again... there are potential encoding problems, plus single ve
From: David Muir [mailto:davidkm...@gmail.com]
On 06/06/11 17:48, Tom Samplonius wrote:
>> Currently - A lot of ISP's are 'stuck' with PHP5.2 or earlier simply
> I don't know if this is really the case.
The problem is much larger than most of us would probably like to believe. Some
of the
On Sat, Jun 4, 2011 at 4:52 AM, David Zülke
wrote:
> Yes, I know. Then why are you and others demanding that the resulting syntax
> be fully compatible with JSON so it could be parsed by other JSON parsers?
> That makes no sense at all. A file with just ["foo"] in it won't be
> interpreted by
On 2011-06-01, Sean Coates wrote:
> > Now, the only reason I would personally support the array shortcut is
> > if it was an implementation of JSON. I know that's not on the table
> > here
>
> I don't think anything is officially off the table, unless we forego
> discussion.
>
> My application is
On 2011-06-01, Michael Shadle wrote:
> On Wed, Jun 1, 2011 at 3:09 PM, Sean Coates wrote:
>
>> This is not about saving five characters every time I type array(),
>> it's about making my systems all work together in a way that's a
>> little less abstracted, and a lot less prone to error.
>
> Why
On Mon, Jun 6, 2011 at 7:12 PM, Lester Caine wrote:
> Pierre Joye wrote:
>
>>
>>> > http://httpd.apache.org/download.cgi
>>> > Win32 Binary IS one of the few binaries Apache supply!!! Some
>>> government
>>> > sites will ONLY allow that version to be installed:(
>>> > PHP5.2 installs hav
On Mon, Jun 6, 2011 at 7:12 PM, Lester Caine wrote:
> Please can you provide a link where THAT statement is made!
Chech the php windows internals list archive as well as the httpd
devel ones. This statement has been written numerous times in both
lists.
--
PHP Internals - PHP Runtime Developme
On Mon, 2011-06-06 at 13:10 -0400, Sean Coates wrote:
> > Please add the RFC header so we know what's the status.
>
> Thanks for catching this.
>
> >> $a = ['one': 1, 'two': 2, 'three': 'three'];
> >
> > has anyone played with the parser to
> > implement it?
>
> I have not, personally. I feel l
Pierre Joye wrote:
> http://httpd.apache.org/download.cgi
> Win32 Binary IS one of the few binaries Apache supply!!! Some government
> sites will ONLY allow that version to be installed:(
> PHP5.2 installs have then been approved for use with the official apache
> install, so are you sa
On Sat, 4 Jun 2011, Andi Gutmans wrote:
> For starters I would bundle ext/mongo which is very well maintained;
> see if we can get "thrift_protocol" contributed to PECL and included
> (support HBase and Cassdandra and used by a few PHP SDKs integrating
> with these data stores).
I generally ag
> Please add the RFC header so we know what's the status.
Thanks for catching this.
>> $a = ['one': 1, 'two': 2, 'three': 'three'];
>
> has anyone played with the parser to
> implement it?
I have not, personally. I feel like it would be a waste of time at this point,
unless a logical problem c
On Mon, Jun 6, 2011 at 6:53 PM, Matthew Weier O'Phinney
wrote:
> My point is that perhaps PHP has missed the boat a bit by moving
> everything into extensions. Perhaps if an extension is particularly
> popular, it should be incorporated into core. But let USAGE drive that,
> not the opinions of i
Forgot to keep the list on this one.
On Mon, Jun 6, 2011 at 11:19 AM, Mike Willbanks wrote:
> A while ago I submitted a patch to allow session_set_save_handler() to
>> accept a class, and support the inheritance of the default session
>> handler's methods.
>>
>> The RFC has a more detailed descr
On 2011-06-05, Pierre Joye wrote:
> It sounds like persons doing these inquiries do not know PHP, its
> environment and how it works, neither they know that 99% of the linux
> distribution (and in some extend on windows too) provide most of the
> modern extensions with their standard distribution
On 2011-06-05, Pierre Joye wrote:
> On Sun, Jun 5, 2011 at 1:09 PM, Hannes Magnusson
> wrote:
>
> > I can't think of a statement I would disagree more with. These are
> > exactly the ones we should be bundling.
>
> > > My reasoning is simple. The key for bundling extensions is to have
> > > them
On Mon, Jun 6, 2011 at 6:48 PM, Lester Caine wrote:
>
> http://httpd.apache.org/download.cgi
> Win32 Binary IS one of the few binaries Apache supply!!! Some government
> sites will ONLY allow that version to be installed :(
> PHP5.2 installs have then been approved for use with the official
Hi!
Currently off the shelf, 5.2.17 is the 'old stable' but for some windows users
it IS the only available version. Changing the rest of the infrastructure to
5.2.17 is unsupported. It is announced on php.net. Now, some Windows
users, due to certain choices, may have to run this version - bu
Pierre Joye wrote:
*WE* recommend using Apachelounge builds of apache, but some sites simply
> will not use that as it is not the recommended build from Apache. They
> religiously follow the rules printed on the official distributions and the
> download page is an official document as far as
hi Sean,
Please add the RFC header so we know what's the status.
Some comments:
> $a = [1,2,'three'];
I liked the existing RFC
(https://wiki.php.net/rfc/shortsyntaxforarrays) so I indeed like it
here too.
> $a = ['one': 1, 'two': 2, 'three': 'three'];
-1, did not like before, I still do not l
On Mon, 2011-06-06 at 12:32 -0400, Matthew Weier O'Phinney wrote:
> On 2011-06-06, Ferenc Kovacs wrote:
> > --00261883a59c62fbe404a50bd89c
> > Content-Type: text/plain; charset=UTF-8
> >
> > On Mon, Jun 6, 2011 at 3:36 PM, Matthew Weier O'Phinney <
> > weierophin...@php.net> wrote:
> >
> > > On 20
On 2011-06-06, Ferenc Kovacs wrote:
> --00261883a59c62fbe404a50bd89c
> Content-Type: text/plain; charset=UTF-8
>
> On Mon, Jun 6, 2011 at 3:36 PM, Matthew Weier O'Phinney <
> weierophin...@php.net> wrote:
>
> > On 2011-06-02, Patrick ALLAERT wrote:
> > > I would like to introduce an E_NOTICE when
On 2011-06-05, Zeev Suraski wrote:
> I'm fine if the entire 'Feature selection and development' part goes
> out of the RFC, but if there's any reference to how features are
> determined, we'd better get it right.
>
> Making changes once we've approved this RFC is going to be much
> tougher. This
On 2011-06-06, Hannes Magnusson wrote:
> On Sun, Jun 5, 2011 at 17:52, Felipe Pena wrote:
> > Reading our bug tracker I noticed a good feature request [1] from 2009 which
> > points to an interesting feature that I think makes sense for us, since we
> > are now working with $f() using objects and
On 3 June 2011 02:18, Arpad Ray wrote:
> Hi,
>
> A while ago I submitted a patch to allow session_set_save_handler() to
> accept a class, and support the inheritance of the default session
> handler's methods.
>
> The RFC has a more detailed description and the current patch:
> https://wiki.php.ne
On Mon, Jun 6, 2011 at 5:18 PM, Larry Garfield wrote:
> For me the question isn't "should we bundle memcached in PHP core", it's
> "how do we establish an expected baseline of PHP components that developers
> can reasonably expect will be available, and what should be in that?" Right
> now, that
On Mon, Jun 6, 2011 at 6:12 PM, Lester Caine wrote:
> Pierre Joye wrote:
>>
>> We use apache and 5.3 smoothly and with the recent addition of rwlock
>> in apc on windows, it runs even better and faster.
>>
>> I'm sorry but unless you provide bugs report with clear reproduce
>> where we can actuall
Pierre Joye wrote:
We use apache and 5.3 smoothly and with the recent addition of rwlock
in apc on windows, it runs even better and faster.
I'm sorry but unless you provide bugs report with clear reproduce
where we can actually try to help you, there is no chance to get
anywhere with this kind o
On 2011-06-03, Dennis Haarbrink wrote:
> One thing I would really like to see in 5.4 is enums.
> There is already an RFC for that: https://wiki.php.net/rfc/enum
>
> This was discussed in february this year, but no consensus was reached.
> IIRC, the most notable problems were:
> - What is the 'valu
On Mon, 2011-06-06 at 10:18 -0500, Larry Garfield wrote:
> The only way, currently, that projects can predict what a given host
> will have installed is "bundled in core PHP". If it's in the core PHP
> bundle, we can *usually* expect it to be there. If not, we can
> *usually* presume it won't
On 2011-06-05, Felipe Pena wrote:
> Reading our bug tracker I noticed a good feature request [1] from 2009
> which points to an interesting feature that I think makes sense for
> us, since we are now working with $f() using objects and strings, and
> the array('class', 'method') is an old known fo
On 2011-06-03, Arpad Ray wrote:
> A while ago I submitted a patch to allow session_set_save_handler() to
> accept a class, and support the inheritance of the default session
> handler's methods.
>
> The RFC has a more detailed description and the current patch:
> https://wiki.php.net/rfc/session-o
On Tue, Nov 30, 2010 at 10:43 AM, Pierre Joye wrote:
> +1, next major version.
>
Just following up on this patch from Nov 2010. Has there been any movement
on this? As it's not committed, I was just wondering what the next major
version would be PHP 5.4, 6, ? As always, I'm happy to provide patc
On Mon, Jun 6, 2011 at 5:18 PM, Larry Garfield wrote:
> On 6/5/11 7:54 AM, Ferenc Kovacs wrote:
>
> just for the record, I agree with Pierre on this one.
>> our userbase has two distinct group: those who are using shared hosting
>> and
>> usually use some third party cms or write their own crappy
On 6/5/11 7:54 AM, Ferenc Kovacs wrote:
just for the record, I agree with Pierre on this one.
our userbase has two distinct group: those who are using shared hosting and
usually use some third party cms or write their own crappy suboptimal code,
and those who use php to build bleeding edge custo
> Can you provide an use case and code example of how that would look?
Sure.
Here's how an ElasticSearch query currently looks in PHP:
$esQuery = new \StdClass;
$esQuery->query = new \StdClass;
$esQuery->query->term = new \StdClass;
$esQuery->query->term->name = 'beer';
$esQuery->size = 1;
// O
hi,
please use pecl-dev to talk about pecl's packages.
Thanks for your work!
On Mon, Jun 6, 2011 at 4:37 PM, Mike Willbanks wrote:
> I've gone through the GeoIP extension and ensured all of the tests now pass.
>
> Bug Report: http://pecl.php.net/bugs/bug.php?id=22749
> Patch File: http://blog.d
I've gone through the GeoIP extension and ensured all of the tests now pass.
Bug Report: http://pecl.php.net/bugs/bug.php?id=22749
Patch File: http://blog.digitalstruct.com/patches/geoip-svn-tests.patch.txt
Also, it looks like the GeoIP extension is based on an extremely old
version, I am going t
On Sun, Jun 5, 2011 at 17:52, Felipe Pena wrote:
> Hi all,
> Reading our bug tracker I noticed a good feature request [1] from 2009 which
> points to an interesting feature that I think makes sense for us, since we
> are now working with $f() using objects and strings, and the array('class',
> 'me
On Mon, Jun 6, 2011 at 3:31 PM, Lester Caine wrote:
> Pierre Joye wrote:
>>>
>>> If you can convince the IT departments of some of the archaic council
>>> sites
>>> > I am having to deal with that they do not have to stress test every
>>> > part of
>>> > a new system ... It's exactly the same ar
On Mon, Jun 6, 2011 at 8:48 AM, Sean Coates wrote:
>
> I was careful in the RFC to indicate that this is *not* JSON, but if others
> feel as strongly as you do about the use of this term, I think it can be
> removed without hurting the idea (as you indicated).
>
Still, it is mentioned so many tim
On Mon, Jun 6, 2011 at 3:36 PM, Matthew Weier O'Phinney <
weierophin...@php.net> wrote:
> On 2011-06-02, Patrick ALLAERT wrote:
> > I would like to introduce an E_NOTICE when an array is silently
> > converted to a string.
> > This isn't very useful as it constantly produces the following string:
On 06/06/11 07:27, Stas Malyshev wrote:
> Hi!
>
>> On 2011-06-05, Pierre Joye wrote:
>>> On Sun, Jun 5, 2011 at 5:52 PM, Philip Olson
>>> wrote:
> I'd to say that I'm very happy to finally see such discussions
> happening, let sort the base (99% is done by our existing RFC about
> rel
> a) JSON is actually being mentioned to advocate for the syntax with for the
> sake of *familiarity*.
> b) Interoperability is being confused with familiarity.
My goal is interoperability. Familiarity is a factor, definitely.
> c) Actual interoperability of the syntax with JSON is just a happy
>
re "JSON"
> · will never validate as JSON
>
> ·recognizablyviolates JSON quoting rules
> · recognizably violates the JSON security concept…
…
> -- I do not feel that the acronym JSON has any clarifying nor edifying
> place in the RFC describing this syntax.
> I have ac
On 2011-06-02, Patrick ALLAERT wrote:
> I would like to introduce an E_NOTICE when an array is silently
> converted to a string.
> This isn't very useful as it constantly produces the following string:
> "Array" and in most of the case, this is a sign of an error.
>
> Let me know about your feelin
Pierre Joye wrote:
If you can convince the IT departments of some of the archaic council sites
> I am having to deal with that they do not have to stress test every part of
> a new system ... It's exactly the same argument FROM them as you are giving
> below as to why we should NOT provide sup
I didn't get any feedback on this.
Does that mean I am on the wrong list or that no one cares?;)
NB: It its not a documentation issue! Patch for Bug #49238 changed the
behaviour.
Am 27.05.2011 11:25, schrieb Lars Schultz:
Hi internals,
Jani told me to ask the list about this. I tried comment
1 - 100 of 119 matches
Mail list logo
