So yes, start from scratch, but why not start from scratch in Perl?

I put it to harshly when I said starting from scratch. . In fact I am dabbling with linux networking stuff: ipvsadm, keepalived.and ip commands and some added configuration layers. Eventually I end up with the same data in different configuration files. keepalived polls services defined by ipvsadm so its configuration file repeats material needed for ipvsadm. Compatibility with installed stuff is a criteria as well.

So It is difficult to decide which configuration file is authoritative for what. Anyway I need to deal with inconsistencies between them. I intend to provide a Perl API to some C code extracted from these commands. But I am not sure I will be given the time to do it. What I want is to avoid to massage many configuration files but to have one that drives everything.

In other words, one should not always work by adding layers on top of layers in Perl (*) but must deal with C to reorganize and/or to provide an clean Perl API.

(*) later edition In Perl or any scripting language. My point was that because some managers know you can pee code in whatever language, they may prefer quick fixes over quick fixes and one ends up in a mess.

-- stefp

In reply to Re: Re: Downside of Perl (relative) popularity by stefp
in thread Downside of Perl (relative) popularity by stefp

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.