Strict and warnings: which comes first?

Replies are listed 'Best First'.
Re: Strict and warnings: which comes first? by Lotus1 (Vicar) on Nov 07, 2019 at 21:33 UTC
Other choices: It depends on where I copy the program from. What are strict and warnings? Neither, I like surprises. Neither, those things hurt job security.	[reply]
Re^2: Strict and warnings: which comes first? by LanX (Saint) on Nov 08, 2019 at 11:46 UTC
> Neither, those things hurt job security. hmm ... actually it never occurred to me that secretly deleting strict and warnings before delivering code might be a clever move. xD Cheers Rolf _{(addicted to the Perl Programming Language :) Wikisyntax for the Monastery FootballPerl is like chess, only without the dice}	[reply]
Re^3: Strict and warnings: which comes first? by Eily (Monsignor) on Nov 13, 2019 at 16:41 UTC
That's because you get better results by deleting your colleagues.	[reply]
Re^4: Strict and warnings: which comes first? by LanX (Saint) on Nov 13, 2019 at 17:21 UTC
Re: Strict and warnings: which comes first? by jcb (Parson) on Nov 07, 2019 at 23:48 UTC
I usually make those the first two non-comment non-blank lines in the file; and I put `use strict;` first as a matter of aesthetic taste — that both puts them in alphabetical order and gives a nice visual lead towards the right, where the later `use` statements are likely to end, since most module names are longer than `warnings`. Example: `use strict; use warnings; use Storable;` [download] Some very useful modules break this pattern: `use strict; use warnings; use DBI; use Tk;` [download]	[reply] [d/l] [select]
Re^2: Strict and warnings: which comes first? by tobyink (Canon) on Nov 08, 2019 at 12:47 UTC
I usually put a `use VERSION` line before them. Most of my modules start off with something like: `use 5.008; use strict; use warnings;` [download] ... before even the `package` statement. toby döt ink	[reply] [d/l] [select]
Re^3: Strict and warnings: which comes first? by jcb (Parson) on Nov 09, 2019 at 00:25 UTC
You are right: I think of `package` as part of the file header, so it goes in the very first line in a module, like the `#!` line in a script. I think that most of my code would probably run under 5.6, so my scripts generally lack `use VERSION`. I may need to see about changing that. :-)	[reply] [d/l] [select]
Re^4: Strict and warnings: which comes first? by tobyink (Canon) on Nov 09, 2019 at 14:54 UTC
Re^5: Strict and warnings: which comes first? by jcb (Parson) on Nov 10, 2019 at 00:00 UTC
Re^5: Strict and warnings: which comes first? by haj (Vicar) on Nov 09, 2019 at 15:51 UTC
Re^3: Strict and warnings: which comes first? by BillKSmith (Monsignor) on Nov 22, 2019 at 23:57 UTC
In my environment, I prefer to specify 'feature' rather than 'version' in part because it is much easier to specify correctly. When a module fails due to compatibility issues, 'feature' helps a maintenance programmer modify the module for an older perl. (If he choses to upgrade perl, he will probably upgrade to the newest version and not care about what is the oldest one he can get away with.) I do understand that 'version' is required by many development tools. That does not apply to me - at least not yet. Bill	[reply]
Re^4: Strict and warnings: which comes first? by tobyink (Canon) on Nov 23, 2019 at 10:07 UTC
Re: Strict and warnings: which comes first? by cavac (Vicar) on Nov 13, 2019 at 07:51 UTC
In my code, i use (updateable-by-script) boilerplates: `#---AUTOPRAGMASTART--- use 5.020; use strict; use warnings; use diagnostics; use mro 'c3'; use English qw(-no_match_vars); use Carp; our $VERSION = 2.3; use Fatal qw( close ); use Array::Contains; #---AUTOPRAGMAEND---` [download] ...and yes, i still need to switch to autodie `perl -e 'use MIME::Base64; print decode_base64("4pmsIE5ldmVyIGdvbm5hIGdpdmUgeW91IHVwCiAgTmV2ZXIgZ29ubmEgbGV0IHlvdSBkb3duLi4uIOKZqwo=");'`	[reply] [d/l] [select]
Re^2: Strict and warnings: which comes first? by afoken (Chancellor) on Nov 13, 2019 at 15:42 UTC
`use 5.020; use strict;` [download] `use 5.020` implies `use strict` (since v5.12) and `use feature` (not relevant here), even without loading `strict.pm` or `feature.pm` - see use. Alexander -- Today I will gladly share my knowledge and experience, for there are no sweeter words than "I told you so". ;-)	[reply] [d/l] [select]
Re^3: Strict and warnings: which comes first? by cavac (Vicar) on Nov 13, 2019 at 17:09 UTC
I know. But i decided to have "use strict" at the top of every perl file anyway. Just to make sure everyone reading it automatically knows it's in strict mode. `perl -e 'use MIME::Base64; print decode_base64("4pmsIE5ldmVyIGdvbm5hIGdpdmUgeW91IHVwCiAgTmV2ZXIgZ29ubmEgbGV0IHlvdSBkb3duLi4uIOKZqwo=");'`	[reply] [d/l]
Re: Strict and warnings: which comes first? (Simultaneous!) by Anonymous Monk on Nov 07, 2019 at 13:26 UTC
Simultaneous!	[reply]
Re^2: Strict and warnings: which comes first? (Simultaneous!) by LanX (Saint) on Nov 07, 2019 at 17:31 UTC
Sex joke? `sleep 2, print "Ho\n" for 1..42` Cheers Rolf _{(addicted to the Perl Programming Language :) Wikisyntax for the Monastery FootballPerl is like chess, only without the dice}	[reply] [d/l]
Re^3: Strict and warnings: which comes first? (Simultaneous!) by perldigious (Priest) on Nov 07, 2019 at 19:09 UTC
Sex joke? Let the games begin! What does sex have in common with fractional numbers? It's improper for the larger one to be on top. :-) Just another Perl hooker - My clients appreciate that I keep my code clean but my comments dirty.	[reply]


more useful options
	PerlMonks