2010/10/24 Giovanni Giacobbi
>
> Greetings,
>
> in reference to bug #52713 i'd like to inquire you about this decision
> which actually broke my codebase in different parts.
>
> The situation is this one:
>
> class ActiveRecord {
>
> public function __call($method, $args) {
>if ($method == "
On Mon, Nov 1, 2010 at 9:47 PM, Felipe Pena wrote:
> 2010/11/1 Richard Lynch
>
> > On Fri, October 29, 2010 7:47 pm, admin wrote:
> > > WTF is T_PAAMAYIM_NEKUDOTAYIM?
> > >
> > > This has to be THE most asked question by new php developers when they
> > > come across it. Can we please change the
On Tue, Nov 2, 2010 at 7:14 PM, Zeev Suraski wrote:
> As long as it actually works as opposed to just compiling :)
It builds, whether it works as of now with trunk is another question.
But that's something we can test in the next couple of weeks before
its inclusion in trunk.
--
Pierre
@pier
On Tue, Nov 2, 2010 at 7:14 PM, Zeev Suraski wrote:
> On Nov 2, 2010, at 9:13, "André Rømcke" wrote:
>
> > On Tue, Nov 2, 2010 at 9:57 AM, Lester Caine wrote:
> >
> >> Derick Rethans wrote:
> >>
> >>> Actually, Kalle just pointed out that it compiles just fine. In that
> >>> case, I think we sh
On Nov 2, 2010, at 10:43, "Ilia Alshanetsky" wrote:
> We should probably stick with the bison parser for now, at least until
> the lemon matches the speed of the existing solution.
>
+1, and there should also be some clear advantages for making the switch and
introducing risk even once it's fas
On Nov 2, 2010, at 9:13, "André Rømcke" wrote:
> On Tue, Nov 2, 2010 at 9:57 AM, Lester Caine wrote:
>
>> Derick Rethans wrote:
>>
>>> Actually, Kalle just pointed out that it compiles just fine. In that
>>> case, I think we should put it in trunk and in the 5.4 alpha.
>>>
>>
>> As long as i
On 11/02/2010 10:31 AM, Ilia Alshanetsky wrote:
> We should probably stick with the bison parser for now, at least until
> the lemon matches the speed of the existing solution.
+1
--
Sebastian BergmannCo-Founder and Principal Consultant
http://sebastian-bergmann.de/
We should probably stick with the bison parser for now, at least until
the lemon matches the speed of the existing solution.
On Mon, Nov 1, 2010 at 3:41 PM, Etienne Kneuss wrote:
> On Nov 01 15:33:59, Derick Rethans wrote:
>> Hi!
>>
>> Work has been done on rewriting the PHP parser to Lemon in a
+1 to adding APC to trunk, it does compile fine (at least at the moment).
On Mon, Nov 1, 2010 at 3:34 PM, Derick Rethans wrote:
> Hi!
>
> I understand that the general idea is to bundle APC with a future
> version of PHP. Right now, APC doesn't really compile for trunk because
> of internal chang
On Tue, Nov 2, 2010 at 9:57 AM, Lester Caine wrote:
> Derick Rethans wrote:
>
>> Actually, Kalle just pointed out that it compiles just fine. In that
>> case, I think we should put it in trunk and in the 5.4 alpha.
>>
>
> As long as it is disabled by default and can easily be replaced by
> prefer
Stas - quick question - what is a PEP?
Is the best way forward for this. I think some discussion about what we want
this to achieve and maybe a rough idea of how it could be done would be a good
start. Not sure it would fit into an RFC (correct me if'm wrong).
Also if this conversation needs to
Derick Rethans wrote:
Actually, Kalle just pointed out that it compiles just fine. In that
case, I think we should put it in trunk and in the 5.4 alpha.
As long as it is disabled by default and can easily be replaced by preferred
alternatives ... eaccelerator is still working fine now that it
12 matches
Mail list logo
