Mark, would you consider having the unfinished-material available for fee?

I am a big fan of "Perl program repair shop and red flags" articles and been waiting for a while for more articles on line or actual book to come out
Unforunately, I feel that I learn more about writing Perl from those articles than reading any articles or books
I brought a whole bunch of perl books after finishing "Learning Perl" because I needed to write longer and complicated programs.

My honest opinion(?) with no CS background, is that all these perl books are not that helpful when it comes to teaching people how to
top down design and come up with algorithm and putting codes together.
And that’s why now I am going back to my pascal course that I took almost 13 years ago to help me understand the algorithm and way to design.
Someone suggest to me that reading someone else’s program is the best way to learn and after reading "redflag series", I feel that there should be more books with real programs(since locating just right program for me to learn from of someone else’s code is not that easy) explaning things rather Than typical Perl books that out there.

---

---

• 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.