james2vegas++ Thanks for the pointer. Using
AnyEvent::Handle looks like it would give me lots of possibilities, particularly if I wanted to chase down Message 6 in some way. That's a bit beyond my current scope right now, but it's a definite candidate for the evolution path.
bingos++ It's good grounding to reinforce what POE::Filter::Line was designed to do. I sort of scooched beyond that by utilizing InputRegexp to do simple message parsing. It seems to work well for what I want, but I'm confused about why some of the regexp's don't work as I expect them to...
One specific thing that is particularly confusing to me is why using either of the following two lines give different results.
InputRegexp=>"\n(\\*\\*\\*)|(\\+\\+\\+)\\s+",
InputRegexp=>"\n(\\+\\+\\+)|(\\*\\*\\*)\\s+",
Now granted, my regexp brain cells still need work, but shouldn't I be getting the same results using either? Maybe I'm I not using this correctly?
Thanks
-Craig
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.