The real, classic mistake is looking at the outputs and finding them wrong, but not looking at the input, not testing it in the debugger or playing with it in an interactive session.

You weren't getting the results you wanted in @ads, but never verified what you started with in $ads. If the data is wrong, a correct split will not produce the expected results.

You might have used the debugger to interact with your program: perl -d ads.pl. You can also start up the debugger without a program, to experiment with commands: perl -demo. ( Actually it should be perl -de 0, but what you give after the -e doesn't matter, and demo is rememberable.)

As Occam said: Entia non sunt multiplicanda praeter necessitatem.

In reply to Re: Parsing an email address by TomDLux
in thread Parsing an email address by gitano

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.