Aran Deltac wrote: > I've just commited a script that uses Class::C3 to pick out the > inheritance order and digs out the methods in the various modules and > creates a nicely formatted POD of inherited methods. Its in: > > http://dev.catalyst.perl.org/repos/bast/branches/DBIx-Class-current/maint/inheritance_pod.pl > > I've used it to generate the INHERITED METHODS section in all the > modules in the DBIx-Class-Tree repo (just commited).
You're a hero! I'll try this on lots of things :) >>>>A DAG is a bit of a different beast than a Tree, but I'll keep it in >>>>mind. Sounds like a deffinate possibility. >>>Well, a tree is a special case of a DAG, so an interface that can handle >>>DAGs can handle trees, but not necessarily vice versa. >>From a user's point of view a tree is just a DAG constrained to a single >>parent, right? > > Sounds right to me. Pretty much. Each node must have exactly one parent (with a fudge at the root) and the graph must be connected (i.e. it's not a forest) Cheers, Dave _______________________________________________ List: http://lists.rawmode.org/cgi-bin/mailman/listinfo/dbix-class Wiki: http://dbix-class.shadowcatsystems.co.uk/ IRC: irc.perl.org#dbix-class SVN: http://dev.catalyst.perl.org/repos/bast/trunk/DBIx-Class/
