It's an interesting concern and should probably remain up to the whim of the individual poster, but I like your solution of shifting the boilerplate to your sig.
FWIW, I don't use say because the very, very small benefit it gives is far outweighed (for me) by the portability constraints. I think it would be fine to use it if the OP uses it or if the OP's code implies a recent enough version where it won't give an error.
I think it is always worth including strict and warnings in any sample code other than a one-liner. If every example of code a novice sees includes these pragmas then even the slowest student will eventually twig that having them in there must be considered A Good Thing. Doing so also has the added advantage that I expect to see it in my own code or third-party code on which I am working and any absence there will become even more noticeable as a result.
All just my opinions, of course.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
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:
Outside of code tags, you may need to use entities for some characters:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, 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, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||