comment on

I don't feel I know enough yet about Perl.

The only way to learn more is to do it more. The next time you need to whip something up and think to do it in a language other than Perl, try using Perl instead.

Be sure to search CPAN to see what you can use to make it easier. I often find that for small, 'whipupitude' programs, a CPAN module synopsis is often 75% of what I need.

Once you get used to using modules, you can start delving into them and improving upon them as you find that they just don't work quite as you'd like.

Other good advice can be found here:

-xdg

Code written by xdg and posted on PerlMonks is public domain. It is provided as is with no warranties, express or implied, of any kind. Posted code may not have been tested. Use of posted code is at your own risk.

In reply to Re: Real Life Perl Exercises by xdg
in thread Real Life Perl Exercises by mikasue

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.


Perl: the Markov chain saw
	PerlMonks