I love this site!

it appears that everyone has contributed in some way to that question I posted. The configuration file that I'm trying to parse is a proprietary log filter configuration file created by CheckPoint. I'vei searched for various perl modules or what not that can parse the data, and get it into perl so I can parse various log files automagically without having to load up the client/server application that normally does the parsing.

I can possibly dummy down the configuration file i['m dealing with, but I dont necessarily want to post it in a public area. If anyone is interested, please feel free to Private Message me and i'll see what I can cook up.

There's a real perl guru here where I work, unfortunatly I dont really want to bother him too much. He's gotten me to the point of getting the data into perl via the Parse::RecDecent module. Now I just need to figure out how to access the data I need out of that complex data structure.

Really, the information I need is only three things from each selection rule, the "type", "val" and "is". Type always returns a scalar value. val can either return a scalar, or list, and "is" is boolean (either data is included from this selection rule, or excluded from the output).

I realise trying to answer a question when posted in a vague way is difficult, and I appologize. After having this issue rack in my brain all weekend long, I've realized how compledx a question I've posed, and that it's d*mn near impossible to solve without an example of the data source, or datastructure returned by data::dumper.

Let m e see what I can cook up with a dummied down version of the configuration hash, and I'll send it to whomever is interested.

Regards,

-=-GardRail-=-

In reply to Re: Re: searching complex data structures by GardRail
in thread searching complex data structures by Anonymous Monk

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.