On Sat, Jan 26, 2013 at 9:26 AM, Anthony Ferrara wrote:
> Pierre et al,
>
> I would prefer to have it in pecl and merge once ready/cleaned up.
> > Yes, same idea than with APC, except that it could be faster (for what
> > I read, waiting to see the sources). Also we can review and do the
> > chang
On Fri, Jan 25, 2013 at 8:05 PM, Pierre Joye wrote:
> On Fri, Jan 25, 2013 at 7:53 PM, Rasmus Lerdorf
> wrote:
> > On 01/25/2013 10:49 AM, Zeev Suraski wrote:
> >
> >> Ok, I'll write up an RFC, and in parallel we'll try to figure out the
> >> mechanics of actually making it happen.
> >
> > Commi
On Fri, Jan 25, 2013 at 5:47 PM, Will Fitch wrote:
>
> On Jan 25, 2013, at 11:25 AM, Zeev Suraski wrote:
>
> >> Either by a number of people stepping up to help with the existing APC
> > code, or
> >> perhaps more realistically making it a priority in PHP 5.6 to streamline
> > the
> >> engine an
On Fri, Jan 25, 2013 at 9:19 AM, Rasmus Lerdorf wrote:
> On 01/24/2013 11:56 PM, Ralf Lang wrote:
> >> From what I understood from Rasmus the biggest challenge with merging
> APC
> >> into core is the fact that the compiler currently isn't built to support
> >> opcode caching. One of the challeng
Hi Internals,
PHP 5.5.0alpha4 has been tagged today. This
release contains bug fixes against alpha3, and adds the
class name resolution via scalar and the DateTimeImmutable
The packages can be found at:
http://downloads.php.net/dsp
As you know, you may read the NEWS file in the source tree f
Hi Internals,
PHP 5.5.0alpha3 has been tagged today. This
release contains bug fixes against alpha2, as well as
new features in existent APIs.
The packages can be found at:
http://downloads.php.net/dsp
As you know, you may read the NEWS file in the source tree for full
changelog
of this rele
On Wed, Jan 9, 2013 at 6:06 PM, Derick Rethans wrote:
> On Wed, 9 Jan 2013, Anthony Ferrara wrote:
>
> > Rasmus wrote:
> >
> > > This is my worry as well. Especially when it comes to opcode cache
> > > support. Most of the patches I see these days completely ignore the
> > > opcode cache side of
On Fri, Dec 21, 2012 at 1:51 AM, Adam Harvey wrote:
> On 21 December 2012 01:26, jpauli wrote:
> > We just tagged PHP 5.5.0alpha2 today. This
> > release contains bug fixes against alpha1, as well as
> > new features.
>
> Are we going to have a news post for this on the Web site?
> (Alternative
On Thu, Dec 20, 2012 at 9:30 PM, Hannes Magnusson <
hannes.magnus...@gmail.com> wrote:
> From: jpauli
> Date: Thu, Dec 20, 2012 at 9:26 AM
> Subject: [PHP-DEV] PHP5.5.0alpha2 release
> To: PHP Internals
>
>
>
> I would appreciate that you would use your full real name now that you
> are represen
I agree with Johannes and Oracle/MySQL people : ext/mysqli must be the
preferred way to replace ext/mysql.
PDO lacks advanced features which wont be available because of PDO
internals incompatibility.
ext/mysqli is a true MySQL internal API exposure into PHP user land, PDO is not.
Moreover, ext/m
Hey,
I've seen Kalle's patch for http://bugs.php.net/bug.php?id=52555.
It actually implements a http_response_code() function to export the
current HTTP response code from SAPI layer to PHP user land.
I'm suggesting to rename that function to get_http_response_code(),
and implement its sister : s
I wrote about ZendMM some time ago
(http://julien-pauli.developpez.com/tutoriels/php/internals/zend-memory-manager/)
, that's in french language ;-)
To shorten the conversation a little bit, I would suggest to trace the
memory with valgrind/massif. That's not too hard if you know what you
do, if n
+1 , nice job
Julien
On Mon, Jun 6, 2011 at 12:53 PM, David Zülke
wrote:
> <3
>
> David
>
>
> On 05.06.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
Seems like leak.
Try disabling ZendMM to see if something noticeable happens (memory
peak should be lower).
USE_ZEND_ALLOC=0
Cheers,
Julien
On Sun, Jun 5, 2011 at 2:01 PM, David Zülke
wrote:
> Smells like a memory leak if gc_collect_cycles() doesn't fix it.
>
> David
>
>
> On 05.06.2011, at 00:
Agree with Derick, strictly speaking, in maths science, INF != INF.
But I dont care if PHP tells me than yes, because PHP is not designed
to solve high level maths problems :)
Cheer,
Julien.Pauli
On Fri, May 27, 2011 at 4:48 PM, Derick Rethans wrote:
> On Thu, 26 May 2011, Scott MacVicar wrote
I remember error messages have been improved since last decade, but
they were engine ones.
Parser ones have never been touched, so to improve them, I +1 your
idea Felipe :)
Julien
On Mon, May 16, 2011 at 7:52 PM, Florian Anderiasch wrote:
> On 16.05.2011 14:15, Felipe Pena wrote:
>> Other exampl
All right ;-)
Johannes: Thanks for details about lighhtpd's internals.
Julien.P
2011/4/27 Johannes Schlüter
> On Wed, 2011-04-27 at 15:36 +0200, Julien Pauli wrote:
> > I'm +1 with that list.
> >
> > I'd like to have some time to work on a lighttpd sapi if
I'm +1 with that list.
I'd like to have some time to work on a lighttpd sapi if possible (haven't
seen lighttpd API yet). If someone got the same idea, just tell it...
What about apache2filter SAPI ?
Julien.P
2011/4/24 Pierre Joye
> 2011/4/24 Rasmus Lerdorf :
> > On 4/24/11 4:41 AM, Pierre Jo
You should take care not to mistake the GC and the MM, they are two
different things and surprisingly, they dont interact with each other.
Zend GC is a layer above Zend MM, and Zend GC can be totally disabled,
Zend MM cant at all.
Zend MM is a BIG layer over malloc()/free() which goals are mainly
Ow, what a crap idea ... You want to make the same php4-written source
code run with PHP4 AND PHP5.3 ?
That seems like an unsolvable challenge, I think that even if you dont
mind very bad codes/stuff you won't make it fully work for production
without alarms every minutes ...
Good luck,
Julien
ime).
J.Pauli
On Wed, Dec 15, 2010 at 12:58 PM, Jon Davey wrote:
> 2010/12/15 Julien Pauli
>>
>> Well, I would say that if your problem is memory, you should consider
>> threads as they all share the same memory space in their process.
>>
>> Apache's childre
Well, I would say that if your problem is memory, you should consider
threads as they all share the same memory space in their process.
Apache's children can weight very heavy if PHP's been compiled to
support lots of extensions, you can happen with ~40/50Mb per process
which is very huge. Conside
I don't remember the source, refresh my mind quickly please :
What happens if variables_order doesn't content 'P' ? Is the data
still duplicated into memory ? I know that $_POST is still there but
is an empty array in that case.
And yes, I'm +1 for such a patch :)
J.Pauli
On Tue, Dec 7, 2010 at
I guess serialize mechanism cant use any char that can be part of a
PHP variable. And "_" can. As property names respect binary
compatibility, the only char that can be used to mark private
properties is actually the NULL byte. Ping me if I'm wrong.
But I'm +1 for improving the serialize() speed,
Care should be taken in the case of new myClass()->foo() just creates
an object to call a method but a static method would be more efficient
here.
However, well used (fluent interface for exemple) make me think +1 for
that patch.
J.Pauli
On Mon, Nov 29, 2010 at 12:40 PM, Felipe Pena wrote:
> Hi
Is this related to http://www.ush.it/2009/02/08/php-filesystem-attack-vectors/ ?
That's a quiet old bug, I'm happy to listen it's now worked on and has a patch.
J.Pauli
On Tue, Nov 16, 2010 at 12:34 PM, Pierre Joye wrote:
> hi,
>
> On Tue, Nov 16, 2010 at 7:15 AM, Rasmus Lerdorf wrote:
>> On 1
Well at least I fixed the splweaktypehintingwithautoboxing for the function
to return ++$var instead of $var++ which couldn't make it ;-)
Julien
On Mon, May 31, 2010 at 5:54 PM, Ferenc Kovacs wrote:
> On Mon, May 31, 2010 at 2:42 PM, Lukas Kahwe Smith >wrote:
>
> >
> > On 28.05.2010, at 11:50,
I remember Marcus worked on something like that some time ago. Might still
be into SVN or somewhere I think.
Julien
On Sat, May 29, 2010 at 9:03 PM, Ferenc Kovacs wrote:
> On Sat, May 29, 2010 at 7:34 PM, Zeev Suraski wrote:
>
> > At 20:28 29/05/2010, Chris Stockton wrote:
> >
> > My biggest
On Wed, Nov 18, 2009 at 8:59 PM, Stanislav Malyshev wrote:
> Hi!
>
>> I've just occured a syntax problem in the following script:
>>
>> > class C {
>> public $n = 1;
>> }
>> $o = new C();
>> $o->f = function () use ($o) {
>> echo $o->n;
>> };
>> $o->f();
>> ?>
>>
>> The result of this script
301 - 329 of 329 matches
Mail list logo