I have always found that strict and -w just get in the way when one wants something up fast. Generally when I do this kind of thing I find they complain about specifics which I'm sure are very handy in large hard to manage code, but as I am never in a position where I must write huge apps in perl... I find them more a hindrance than help.

I personally believe that you're perfectly right for definitions of "huge" involving... about ten lines of code. Specifically, the ratio hindrance/utility that strict and warnings give become relevant in:

For anything but these cases, being under strict will most likely just require you to type some three more keys each time a new variable is introduced: something which is unlikely to make you risk a CTS in the first place and will likely save you many editing cycles to correct trivial but common errors, thus reducing the overall number of keystrokes.

Whatever, this is just what quite about everybody think too. Including those who beg to differ due to ignorance first, but then get to know better. Humanity is vast, however, and you may really be one of a kind...

--
If you can't understand the incipit, then please check the IPB Campaign.

In reply to Re^3: Tk::NoteBook issue with creating tabs under a menu by blazar
in thread Tk::NoteBook issue with creating tabs under a menu by thefinn

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.