For things like MMD --- I'd like to traverse the hypertext 'linkbacks' to any given method. Which method *exactly* will get called in the super class? A hypertext documentation system that introspects on classes could help here. Wouldn't it also be good to link back to the modules that use the current module in its operating environment?
I am not sure if Perl6 is capable of that level of introspection without actually parsing the code itself, or running it (like a profiler). I also question if that much depth is always nessecary. Sure in some cases it is, but I would argue that in those cases you should be reading the code anyway.
PPI is slowly getting towards the point where this can be done. I have a VERY early prototype documentation generator with a class tree on the left, and a tabbed right panel that switches between normal POD and auto-generated structural documentation views.
Given that I'm relatively confident some sort of equivalent "document parser" will be doable using a different parsing mode of the Perl 6 parser (I had a conversation with Damian at YAPC.AU last year about this), I'm fairly sure this can be done.
Adam K
