Bill Karwin schrieb:
-----Original Message-----
From: Markus Wolff [mailto:[EMAIL PROTECTED]
Still, having dependency info in the manual would be nice for
the future (hint, hint :-)).
That's not good information to put into a manual, because it is so
likely to become outdated and inaccurate.
It would be better to document how to generate the dependency info
dynamically, or provide a tool to do it.
Depends. If the dependencies were documented with PHPDoc tags, the
information could be part of the generated API. It would be absolutely
sufficient to provide this information on a component-level, which is
what PEAR does - albeit in their package.xml, not in PHPDoc.
The get_included_files() method is great when you really need a list of
all the files that really get included, though. Should have thought
about that ... well, it's *hot* today, my brain doesn't work anyway, so
I better shut up now :-)
CU
Markus
