Hi Stas,
You know, it's not always possible to get new features or performance
boosts without API change. It's one of the reason why we postpone such
changes for major releases. But, I agree that even in major releases API
shouldn't be changed without significant reasons, and we should keep
c
Hi Nikita,
Personally, I don't see any reason to build AST. As you mentioned
yourself, it will be slower and will require more memory. On the other
hand AST itself would allow to perform only very basic optimizations.
Most of them can be easily done on VM opcode level as well.
Also, as it's
Hi Johannes:
On Thu, Jan 19, 2012 at 01:50:47PM +0100, Johannes Schlüter wrote:
>
> unsigned long length
>
> The width of the field. This corresponds to the display length,
> in bytes.
>
> The server determines the length value before it generates the
> resu
Hi!
> To date, I've been basing work, which exposes syntactic structure, on
> phc's maketea grammar (Phalanger's is more up to date, but also more
> complicated what with its provenance and the Linq and generics and all),
> but it's reverse-engineered and certainly wrong (oh, that reminds
> me
On 05/09/12 13:48, Morgan L. Owens wrote:
I'm not a core dev, but I would like to add to the notes above that
"third parties", such as myself, who want to do things with PHP source
other than run it through a PHP interpreter would also appreciate such
a separation of concerns.
To date, I've b
Will Fitch wrote:
On Wed, Sep 5, 2012 at 4:14 AM, Lester Caine mailto:les...@lsces.co.uk>> wrote:
Will Fitch wrote:
Hi, Lester - I'll update the patch and RFC to include this format. This
is the
format I'll use unless others have a better approach:
2012-09
On Wed, Sep 5, 2012 at 4:14 AM, Lester Caine wrote:
> Will Fitch wrote:
>
>> Hi, Lester - I'll update the patch and RFC to include this format. This
>> is the
>> format I'll use unless others have a better approach:
>>
>> 2012-09-01T00:00:00-0500 (America/Chicago)
>>
>
> Just working through ano
OK, apparently we will continue the discussion her.
Pierre Joye in php.internals (Wed, 5 Sep 2012 13:15:43 +0200):
>On Sep 4, 2012 10:25 PM, "Jan Ehrhardt" wrote:
>>
>> Rasmus Lerdorf in php.internals (Tue, 04 Sep 2012 13:15:50 -0700):
>> >Just call error_reporting() at the beginning of your scri
On 2012-09-05 07:57, Nikita Popov wrote:
Hey folks!
Some people asked me what the advantages of using an AST-based
parsing/compilation process are, so I put together a few quick notes
in an RFC:
https://wiki.php.net/rfc/ast_based_parsing_compilation_process
It would be nice to get a few commen
Hi!
forgot to do reply all :)
On Sep 4, 2012 10:25 PM, "Jan Ehrhardt" wrote:
>
> Rasmus Lerdorf in php.internals (Tue, 04 Sep 2012 13:15:50 -0700):
> >Just call error_reporting() at the beginning of your script.
>
> Which ain't possible in drupal (or hardly). You do not write any code.
> You jus
Hi!
> The complexity of the current grammar is working against development.
I'm not sure that undertaking a task of rewriting whole grammar, with
all disruptions etc. that this is going to cause, will speed up
development a lot. But if you want to try it and show how easy it would
be with your gr
Will Fitch wrote:
Hi, Lester - I'll update the patch and RFC to include this format. This is the
format I'll use unless others have a better approach:
2012-09-01T00:00:00-0500 (America/Chicago)
Just working through another backlog of 'todo' items.
Your current RFC includes -0500 in the examp
Hi,
On 04/09/12 21:57, Nikita Popov wrote:
Hey folks!
Some people asked me what the advantages of using an AST-based
parsing/compilation process are, so I put together a few quick notes
in an RFC:
https://wiki.php.net/rfc/ast_based_parsing_compilation_process
It would be nice to get a few com
13 matches
Mail list logo
