On 09.01.2013 13:12, Derick Rethans wrote:
There is a tokenizer for this already that Greg wrote ages ago in
pecl:
http://pecl.php.net/package/docblock - why can't that be extended to
parse your style of annotations in docblocks?
To be honest; I haven't had the time yet to learn and apply
On 08.01.2013 09:55, Stas Malyshev wrote:
First of all, there are already plenty of established userland
implementations - so there is really no need for this.
On the contrary, plenty of implementations means there's a need in
this
functionality, and it might be a good idea to have one
On 08.01.2013 18:19, Yahav Gindi Bar wrote:
That's true. But I wish to state my opinion now: the current
annotations
that Doctorine etc. use is a hack. They took the original doc-block
style
comments and use them for storing metadata. that's the reason I think
that
in case we'll implement
On 09.01.2013 02:38, Rasmus Schultz wrote:
A native implementation of PHP-DOC block parser for run-time purposes
(annotation libraries) is already available in the Reflection API,
There is no DocBlock parser in the Reflection API; you can merely
retrieve the T_DOC_COMMENT token.
and
already
to these constructs.
This document is still an unfinished draft and open for scrutiny by the
community
and stakeholders. It documents the current state of affairs and also
opens up
discussion for future improvements such as Inline DocBlocks.
Please let me know if you have any questions,
Mike van
in token_get_all().
David
On 06.06.2011, at 22:30, Mike van Riel wrote:
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(FILE));
gc_collect_cycles();
var_dump
Before I forget; without gc_collect_cycles I get the following output
using memory_get_usage instead of memory_get_peak_usage:
int(634640)
int(635392)
Mike
On Tue, 2011-06-07 at 19:44 +0200, Mike van Riel wrote:
I have ran the script that you provided and got the following results
Am i then also correct to assume that the output of
memory_get_peak_usage is used for determining the memory_limit?
Also: after correcting with your new information (zval = 114 bytes
instead of 68) I still have a rather large offset:
640952+2165950+114+(276697*114)+(276697*3*114)+2165950 =
To be honest: everybody knows what you mean when you say callback.
Callable sounds more like the name of an interface.
On Tue, 2011-06-07 at 22:32 +0200, David Zülke wrote:
On 07.06.2011, at 22:31, Stas Malyshev wrote:
Hi!
callback is callable, the opposite could not be true.
a string
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(FILE));
gc_collect_cycles();
var_dump(memory_get_peak_usage());
And execute the following bash line preceding:
export
of code for my tests:
var_dump(memory_get_peak_usage());
$tokens = token_get_all(file_get_contents('PATH'));
var_dump(count($tokens));
var_dump(memory_get_peak_usage());
I hope this mail did not scare anyone ;)
Kind regards,
Mike van Riel
--
PHP Internals - PHP Runtime Development
Hey David,
That gives me the following output:
int(640720)
int(244001144)
Mike
On Sat, 2011-06-04 at 23:51 +0200, David Zülke wrote:
What does
var_dump(memory_get_peak_usage());
token_get_all(file_get_contents('PATH'));
var_dump(memory_get_peak_usage());
get you?
David
--
PHP
On 05/31/2011 08:52 PM, Sean Coates wrote:
I'm one of the people who've brought it up on Twitter. Today's discussion seems
to have earned some traction, which is a step in the right direction, I believe.
I would prefer (as Rasmus pointed out) not to start a long discussion about it.
experiences to the efforts.
I hope that my experiences building the Static Reflection for DocBlocks
in DocBlox can prove useful.
--
Mike van Riel
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
On 05/11/2011 03:18 PM, Lester Caine wrote:
Ferenc Kovacs wrote:
as phpDocumentor is dead and doesn't support new things like
namespace and
closures, we should take those into account also.
Nothing stops it from working perfectly well on the years of code that
it still supports! Finding
RAM.
--
Mike van Riel
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
to mind is to search for () or arguments. This
sounds rather hackish to me, might I be missing a solution?
Another question is: when would you like to have this released? PHP-
next? (thus either 5.4, 6, 7 or whichever is next?).
Thank you!
--
Kind regards,
Mike van Riel
--
PHP Internals
your answer faster..)
Bottom line: I'd opt for keeping it.
Kind regards,
Mike van Riel
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
requests.
Kind regards,
Mike van Riel
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
be to also add the docblock template operator but I find it
hard to determine the complexity of this, see
http://manual.phpdoc.org/HTMLSmartyConverter/HandS/phpDocumentor/tutorial_phpDocumentor.howto.pkg.html#basics.docblocktemplate
Kind regards,
Mike van Riel
--
PHP Internals - PHP Runtime
Sufficool, Stanley wrote:
-Original Message-
From: Jille Timmermans [mailto:ji...@quis.cx]
Sent: Monday, March 22, 2010 9:30 AM
To: Sufficool, Stanley
Cc: 'PHP Developers Mailing List'
Subject: Re: [PHP-DEV] [PATCH] Raise warning first on
Maximum execution time exceeded
Op 22-3-2010
Alexey Zakhlestin wrote:
On Wed, Oct 22, 2008 at 5:03 AM, Ryan Panning [EMAIL PROTECTED] wrote:
I've been wondering, is such a thing even possible? Is there a good way to
implement an object destruct order? Here are my thoughts:
In the class definition, specify what level of destruction the
22 matches
Mail list logo
