Beefy Boxes and Bandwidth Generously Provided by pair Networks
Keep It Simple, Stupid

comment on

( #3333=superdoc: print w/replies, xml ) Need Help??
Hello, You all have provided some great ideas on how to tackle cascading defaults. Some solutions have proposed OO possibilities, and others have used procedural methods, although I'm not sure these allow for two levels of defaults as I'm interested in. Now that I've heard some good ideas, I'd like to hear more about what's so bad about the original sort of structure proposed in the question. Here's my analysis of it:


  • It's easy to understand. Because there is no OO abstraction layer, I think what the code is doing is more straightforward, and is therefore more accessible to folks to understand and extend. (Watch me contradict this below in the "Flaws" section)
  • Simple calling syntax. There's no need to initialize an object before calling err and I can type simply err rather than $obj->err, potentially saving a good bit of typing.
  • Awkward interface. I don't like using having the need for a wrapper subroutine in the users module, because it appears to give them a free form interface to manipulate stuff, where with OO you have a clearer interface of what options are valid and what aren't. It could also be construed as confusing to have CGI::Err:err and MyModule::err doing similiar but slightly different things if people didn't understand what was going on.

Thanks! -mark

In reply to How bad is the original proposal? by markjugg
in thread Handling cascading defaults by markjugg

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, 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, 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.
  • Log In?

    What's my password?
    Create A New User
    and the web crawler heard nothing...

    How do I use this? | Other CB clients
    Other Users?
    Others making s'mores by the fire in the courtyard of the Monastery: (8)
    As of 2021-01-28 09:59 GMT
    Find Nodes?
      Voting Booth?