comment on

If you can come up with a 90% solution that covers traditional methods, Moose, Class::Accessor, and Class::Struct, I think you'll be in good shape.

For the rest, provide an easy way for me to specify the methods and other information manually. Either in my code or in another file. For modules I get from CPAN or elsewhere, it would need to be in a separate file that I could reuse between projects (and hopefully share with others). For my own modules, I'd prefer to have a way to embed the infomation in my code, but a separate file would be OK, too.

If you make it easy for me to build a plugin to provide automatic support for my personal method-maker du jour, so much the better.

By the way, thanks for all the effort you are putting into this project.

TGI says moo

In reply to Re: How to find all the available functions in a file or methods in a module? by TGI
in thread How to find all the available functions in a file or methods in a module? by szabgab

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


No such thing as a small change
	PerlMonks