comment on

Oh, several reasons. Most of all, it does some things I think were a major mistake, like trying to determine whether a sub is called as a function or as a method, at runtime.

Furthermore, it has its own "optimization" using AUTOLOAD, defining sub definitions as strings and evalling them at runtime when the sub is first called. Again, it's not something I want to see in every module.

Leave out those major stumbling blocks (for me anyway), and you do get some readable code, I agree. But the module is still too big for its own good.

I'm quite convinced there must be many much better examples of modules to use as a model on how to do things.

In reply to Re^4: What CPAN modules are "good reads"? by bart
in thread What CPAN modules are "good reads"? by tlm

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.


Don't ask to ask, just ask
	PerlMonks