Re: Suggestions for Reflection API
| From: | Marcus Boerger | Date: | Wed, 25 Feb 2004 08:23:03 +0000 |
| Subject: | Re: Suggestions for Reflection API | ||
| References: | 1 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-8115@lists.php.net to get a copy of this message | ||
Hello Sebastian,
Wednesday, February 25, 2004, 8:55:54 AM, you wrote:
> Hi,
> I just looked for the first time in months at the Reflection API and
> have two suggestions:
> 1.) There are a couple of methods that throw an Exception.
> I think it would be better to introduce a Reflection_Exception
> class that is thrown instead of the standard Exception.
> If possible, it might be a good idea to only allow throwing
> Reflection_Exception instances to the internal Reflection_*
> classes.
Have a better look :-) There is already a class 'Reflection_Exception' used
for all throw statements, if not it is an oversight.
> 2.) getVersion() is currently only declared for Reflection_Extension.
> I think it would be nice if we had versioning for classes and
> methods available through the Reflection API, too.
> This could be achieved, for instance, by either introducing yet
> another __-prepended property (const $__version = '1.0.0', for
> example) or by using metadata in doc-comments (@version 1.0.0).
> This would solve the versioning problem that is currently
> discussed on the pear-dev list, IMHO.
Reflection does not scan the meta docs. So just incorporate that into the
next version of phpDocumentor and be done?
regards
marcus