My thanks to revdiablo for his suggestion that I compress the code in the hopes of getting someone to reply. I found it in the process... (/me feels really stupid)

First off, let's review what is "true" in perl.

And, of course, there are those things that everyone forgets now and then... and then kicks themselves repeatedly when they notice it. For example: [] is true. So is {}. After all, it's holding a non-zero value... my trouble serves me right for that little while loop in the get() function of the YuGiOh::Filter package. Once repaired, everything started working...

Well, thanks to everyone who at least tried to help, may we all walk away with a good lesson.





My code doesn't have bugs, it just develops random features.

Flame


In reply to Re: POE Client/Server pairs by Flame
in thread POE Client/Server pairs by Flame

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.