Re^2: Long list is long

A number of problems with the code you posted: Missing strict ... Missing warnings ...

Kudos to kcott for patiently showing by example yet again how to write excellent, clean and succinct Perl code. Unfortunately, it seems unlikely that the monk in question will follow your sage advice, despite a gentle nudge from haukex a year ago.

Given the Bod's recent posting history on this topic:

Re^4: Newline's creep in, while using Tie::File - "is it a universal belief that strictures should be on or a majority belief?"
Backdating strict - "should strict always be used or are there circumstances when it makes sense not to use this pragma?"

I'm trusting that a once similarly recalcitrant Bod has now seen the light and might be persuaded to share his experiences ... along with why (or why not) he uses strict and warnings nowadays.

Oh, and just in case it helps, a non-Perl Monk reference on this topic: Always use strict and warnings in your Perl code (perlmaven)

Update: I also keep a list of references on this topic: use strict and warnings References

Comment on Re^2: Long list is long Select or Download Code

Replies are listed 'Best First'.
Re^3: Long list is long by kcott (Archbishop) on Oct 30, 2022 at 13:34 UTC
G'day eyepopslikeamosquito, Thanks for the compliment. I usually look at an OP's previous posts. This gives me an idea of the OP's level of Perl knowledge and how best to frame my response. I did check on this occasion; wondered if I was flogging a dead horse; but chose to proceed anyway. To Chuma: I've been writing Perl code for almost 30 years. A substantial part of my paid employment involves writing Perl code. I use these pragmata for personal, $work and PM code. I don't do this because it's trendy, expected, or for any other frivolous reasons; I do it because they're extremely useful and save me a lot of time. Even with decades of experience, I still make typos and other silly mistakes (just like everyone else does) — I'd like Perl to tell me about these problems as soon as possible, instead of getting weird or unexpected output and spending a lot of time tracking down the source of the bug. I encourage you to use these pragmata for the same reasons. — Ken	[reply]

Replies are listed 'Best First'.

Re^3: Long list is long
by kcott (Archbishop) on Oct 30, 2022 at 13:34 UTC

G'day eyepopslikeamosquito,

Thanks for the compliment.

I usually look at an OP's previous posts. This gives me an idea of the OP's level of Perl knowledge and how best to frame my response. I did check on this occasion; wondered if I was flogging a dead horse; but chose to proceed anyway.

To Chuma: I've been writing Perl code for almost 30 years. A substantial part of my paid employment involves writing Perl code. I use these pragmata for personal, $work and PM code. I don't do this because it's trendy, expected, or for any other frivolous reasons; I do it because they're extremely useful and save me a lot of time.

Even with decades of experience, I still make typos and other silly mistakes (just like everyone else does) — I'd like Perl to tell me about these problems as soon as possible, instead of getting weird or unexpected output and spending a lot of time tracking down the source of the bug. I encourage you to use these pragmata for the same reasons.

— Ken

[reply]