Hi,
by documenting some SPL classes, and I've got a few suggestions/points
I'd like to discuss
- Automatically group methods per interfaces etc..
- Should we also display interfaces that child classes implements even if
they're intdirectly implemented by their parent class?
basically, if
class A implements Plop {}
should we document B like:
class B extends A implements Plop {}
- Highlight abstract classes/methods (avoid duplication of methods
implemented+abstract?)
Other than whitespaces missing between the type and the abstract modifier,
I believe the fact that one class is abstract should be strongly highlighted.
- Add links on the extends + implements along with links to <classname>
(i.e spl.data structures)
Currently, the OO docs, and especially the inheritance branch is hard
to traverse, adding that kind of links would make it easier.
Additionally we could wonder how and whether we should document
build-in interfaces linked with object handlers.
That way we could rapidly provide basic documentation for every
function implemented in those interfaces.
Regards,
--
Etienne Kneuss
http://www.colder.ch
Men never do evil so completely and cheerfully as
when they do it from a religious conviction.
-- Pascal
