Might. It's on the slope of diminishing returns, though. (And the numbers of different ways to get variables out of the arg array is huge.)
Parent classes and dependencies are machine-document able, fairly easily. They are conceptually similar. And documenting them for a human is usually copy-paste-format in my experience. Trying to automatically document functions may be useful, but it wouldn't be something I'd want to run with the dependency tree. (Which I would want to run on every module I've ever written: It'd make my life simpler.) Functions I'd rather do by hand, usually.
(I guess I'm looking at this as a way to document my code, not code someone else has written that I want to use.)
In reply to Re^5: Deriving meaning from source code, some code is self documenting
by DStaal
in thread Deriving meaning from source code, some code is self documenting
by submersible_toaster
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |