Thanks for your comments and the recommended reading, I see your point and agree, when it matters the best solution for the job is the only way to go, and I one thing i do know is anything I produce definitely isn't that!.

I do use modules various things, but I try to get a good hold on what core perl can do for me, then I look for modules to do it better and easier in the future. I'm constantly dropping my ways of doing things for a better method or implementation, sometimes by way of a module. on the other hand sometimes I find a function I've already done is already implemented in a module but prefer my method because it's more relevant to my application.

Please understand the work I am doing with perl here is VERY non critical, their just bits a pieces to be of use to my fellow employees. Sometimes I could have downloaded a whole application to do what I've done, but it wouldn't have everything I need and I couldn't easily modify it for my own purposes.

I work in a call center environment and perform many other tasks of which (thankfully) I do better than programming, but this is what is increasingly catching my interest and where I am leaning towards in my career. hopefully when I am doing more serious work with perl, I will be doing things ethically,

thanks for your advice

In reply to Re: (Ovid) Learning or being unethical? by whahoo
in thread REGEX: muliple search and replace by whahoo

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.