From: Sean Quinlan <[EMAIL PROTECTED]>
Date: Wed, 08 Sep 2004 11:25:07 -0400
Although I haven't personally come across the need to have multiple
scripts have re-used command line options yet (other than a few old
historic cases), this sounds like an interesting project for handling
those times when it might be the case. And certainly is a great
intellectual exercise for sharing documentation for any set of inherited
classes - assuming I understood your intent correctly from my first
quick read. ... Composite Documentation?
Close enough.
Actually, if I understand your intent correctly (I'll take a more
detailed read tonight), might it be more interesting to provide a
generalized way of inheriting the POD documentation (or some specified
subset) for any inherited class? Perhaps source filtering to go extract
the POD wherever 'use Module' occurs? . . .
Yes, but then you're confronted with the problem of how to integrate the
pieces, never mind distinguishing end-user documentation from module
documentation (which also ought to be there). By contrast, options are
small, mostly independent, heritable in an intuitive way, and can be
combined simply (if not always ideally) by sorting them alphabetically.
-- Bob
_______________________________________________
Boston-pm mailing list
[EMAIL PROTECTED]
http://mail.pm.org/mailman/listinfo/boston-pm
