Re^2: Tk::NoteBook issue with creating tabs under a menu

Replies are listed 'Best First'.
Re^3: Tk::NoteBook issue with creating tabs under a menu by jethro (Monsignor) on Jul 15, 2008 at 16:20 UTC
-w warns about things looking like an error, in short things you can but should not do. Fine for hacks, but anything more than 10 lines is already way past that point IMHO Do you really believe that when your test code matures to a bigger and bigger program that on a fine sunny day you will sit down and convert that code to use strict and -w? Probably not. That's why it is better to do "the right thing" from the beginning and get used to it	[reply]
Re^3: Tk::NoteBook issue with creating tabs under a menu by toolic (Bishop) on Jul 15, 2008 at 21:39 UTC
I have always found that strict and -w just get in the way when one wants something up fast... I find them more a hindrance than help... I just don't see a need for the added drama associated with strict. I felt the same way, a few years ago. I am never in a position where I must write huge apps in perl Neither am I. But, I always use warnings and strict now. I developed the habit of declaring all variables with my that it is now second-nature: I don't even realize I'm typing it. And, I fix all warnings because every single warning has pointed to a bug in my script. One day, you may even find this poem humorous :)	[reply]
Re^4: Tk::NoteBook issue with creating tabs under a menu by FunkyMonk (Bishop) on Jul 15, 2008 at 22:19 UTC
There's always `use warnings FATAL => 'all'`. I wouldn't program Perl without it. Unless I state otherwise, all my code runs with strict and warnings	[reply] [d/l]
Re^4: Tk::NoteBook issue with creating tabs under a menu by thefinn (Initiate) on Jul 16, 2008 at 04:30 UTC
Hilarious poem.	[reply]
Re^3: Tk::NoteBook issue with creating tabs under a menu by Anonymous Monk on Jul 16, 2008 at 07:47 UTC
Use strict warnings and diagnostics or die	[reply]
Re^3: Tk::NoteBook issue with creating tabs under a menu by blazar (Canon) on Jul 16, 2008 at 16:34 UTC
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: one liners; golf (unless the specific rules say otherwise, but I can't remember such cases;) obfu (but IME it's a pleasure when the code is compliant anyway.) 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.	[reply] [d/l]