[Catalyst] Test::WWW::Mechanize::Catalyst and POST

[Aran Deltac]

We have this issue in DBIx::Class as well - there are many levels of
inheritance and looking at a single module's methods can be confusing.
 To eleviate this I wrote a script (maint/inheritance_pod.pl) which
traverses the Class::C3 inheritance structure and produces some nicely
formatted POD, like this:

INHERITED METHODS
  DBIx::Class
    *   mk_classdata
    *   component_base_class
  DBIx::Class::Componentised
    *   inject_base
    *   load_components
    *   load_own_components
  Class::Data::Accessor
    *   mk_classaccessor

If someone wants more detail they just click on the method and they'll
be taken to the documentation for it.  Something like this could
potentially be developed that would be compatible with Catalyst (which
does not use Class::C3).  Also, it would be fairly trivial to
automatically updated the "INHERITED METHODS" section of all the
modules in a release, so that the list does not fall out of date.

Aran

On 5/20/06, Leon Brocard <acme at astray.com> wrote:
> On 5/15/06, Michael Alan Dorman <mdorman at tendentious.org> wrote:
>
> > I totally agree, and I also agree with Matt that the right thing to do
> > is hit Leo with a "Why are you cutting and pasting the docs for
> > T::W::M, shouldn't you just point to them" bug.
>
> I can't win! If I put my superclasses' methods in, people complain
> that they are out of date or not entirely complete. If I don't, people
> will have no idea what methods to use. I thought I'd reached a good
> compromise... ;-)
>
> Leon
>
> _______________________________________________
> Catalyst mailing list
> Catalyst at lists.rawmode.org
> http://lists.rawmode.org/mailman/listinfo/catalyst
>