comment on

> It doesnt matter how it reads/writes, as long as the output is coherent

Sorry I don't know what that means. °

Can you output each service independently or do you need to know all the data before writing?

My approach would be using a flip-flop operator to read each service and to output at the end.

Each line would be processed by a dedicated subroutine based on the first word.

Like service::description() and so on.

This would make your code far more readable and easier to maintain.

Cheers Rolf
_{(addicted to the Perl Programming Language :)

Wikisyntax for the Monastery}

°) I can help you with Perl, but not with Cisco or Juniper, sorry.

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.