Re^2: value disappears in if statement

Replies are listed 'Best First'.
Re^3: value disappears in if statement by trippledubs (Deacon) on Mar 10, 2015 at 04:34 UTC
Re: Programming Jobs, use strict or do not pass go	[reply]
Re^4: value disappears in if statement by Anonymous Monk on Mar 10, 2015 at 07:57 UTC
hi trippledubs, so your answer is because Your Mother mother said so? This is the sequence OP: I have question ... short code A: you should use strict Why should the OP use strict? There are no errors in OPs posted code that strict would catch, talking about strict is a distraction ... adding `use strict;` causes the OPs program to die with errors and will not help him solve any problem in the posted code Adding "use strict;" without any elaboration is the easiest type of comment/reply to make to any perl programming question, and it usually just makes the OPs program die ... and the OPs usually not ready to understand how to benefit from strict Is strict useful? Yes, I used it here cause I always use it Useful to the OP? I doubt it	[reply] [d/l]
Re^5: value disappears in if statement by Anonymous Monk on Mar 10, 2015 at 13:08 UTC
Adding "use strict;" without any elaboration is the easiest type of comment/reply to make to any perl programming question, and it usually just makes the OPs program die You seem to have missed that the node in question answers the OP's problem and contains a link to Use strict and warnings. To always `use strict` is good advice the same way that to always look both ways when crossing a street is good advice, even when it's a one way street: because it's a good habit to get into. And it might save you some pain someday: `https://www.youtube.com/watch?v=0Lm9TPym9A4`	[reply] [d/l] [select]