comment on

I don't have a problem with "Perl Golf" short solutions ...:-)

There is nothing even remotely "Perl Golf" about that, IMHO that is practically a slur against perl, practically anti-perl-propaganda :)

However its obvious the OP (Original Poster) is not talking about those basic sorts of problems.

Sure its not :) Take for example Watching long processes through CGI (Aug 02), nothing particularly basic about it, sure its got 2 functions, but most of the code isn't in functions, less than 100 lines

Or take for example Text-CSV_XS-0.97/examples/csv2xls, 200 lines, one function( usage(), mostly string/heredoc)

Its easy to well past 1000 lines with this type of program, and its obvious to me this is the type of program the OP is talking about -- doesn't need modules or Test:: anything

In reply to Re^4: Developing code to be a module (perl -lanse) by Anonymous Monk
in thread Developing code to be a module by rpnoble419

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.


Welcome to the Monastery
	PerlMonks