|Problems? Is your data what you think it is?|
Opps! I did it again. Had an opinion that is. I should probably not answer this, but it's simply too provocative.
In reverse order:
I would tell them that I cannot help them with that, but that I had heard that Matt's script are notoriously difficult and dangerous to use and suggest that they might find it easier to visit NMS instead.
First Perl did not have
Many of perl's native abilities can be be dangerous if used incorrectly, or as in the case cited by MJD in your reference, used without proper forethought for the consequences.
Finally, I never advocated doing anything blithely. I think said,
I would usually say something to the effect of:
Are you sure that's what you want to do? If your sure, read Perlref and by the time you've done so, you will probably understand how to do it, but more importantly why you almost certainly don't want to. Beyond that, if you'd care to explain a little more about why you want to do this, someone may be able to show you a better way to acheive your goals.
I realise some would read that as patronising, but if they do, that's their problem not mine.
First off, I don't know. I can hazard a good guess, but they know better than I and as you point out, it is their codebase
After much typing and deleting, I've decided to pretend that pair of questions was not asked. If you want to have a serious and deep debate on a very awkward subject, I'm sure we can find somewhere more suited to that than PerlMonks.
And I guess that is a lesson in its self. Noone is forcing us to answer either way. Likewise, if I choose to give what I think is 'good advice' and it is rejected, I tried. It's enough. Perl doesn't enforce good practice, hence warnings, and strictures are optional. Personally, I'd probably invert the default, but I'd still make it optional.
Updated to close UL tag and correct brain fart.
Examine what is said, not who speaks.
The 7th Rule of perl club is -- pearl clubs are easily damaged. Use a diamond club instead.