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+",
[download]

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

---

---

• 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.