Re: ce->doc_comment and ReflectionClass::getDocComment
| From: | Johannes Schlüter | Date: | Sat, 28 Feb 2009 18:52:50 +0000 |
| Subject: | Re: ce->doc_comment and ReflectionClass::getDocComment | ||
| References: | 1 2 3 | Groups: | php.pecl.dev |
| Request: | Send a blank email to pecl-dev+get-6178@lists.php.net to get a copy of this message | ||
On Sat, 2009-02-28 at 19:22 +0100, Piotr Pokora wrote:
> Change is easy. Problem is, that (even if you fix it) , it will be
> available in distros in next few years.
> Which means you can forget about efficient documentation system.
If distros and their upgrade speed would be relevant for what I'm doing
I'd do nothing. Why should we develop PHP at all? - I can't see that
point. And *I* don't care too much about distro users - most distros
broke stuff in the past ...
> > Not sure whether there are other things to consider and whether there's
> > a reason.
>
> If ZEND_ARG_INFO provides info for reflection, what is the sense to
> provide only part of it?
> Number of required arguments is a nice thing, even human readable
> argument names are.
> But both are quite useless to make real documentation.
Well the engine needs the information whether a parameter is passed by
reference and telling the engine about type hints is beneficial, too.
(thinking about inheritance) so there's a technical need for most of the
arg info. That *need* isn't there for doc_comments and things like the
--rc flag for the PHP CLI are way newer than the doc_comment support,
back then self-documenting PHP wasn't a topic.
> Anyway, I can provide access to doc_comment via own extension, but would
> be cool if there's something wrong with this member.
Don't understand what you mean.
johannes