note
diotalevi
<p>I find myself using strict less and less often but only in constrained circumstances. Small scripts, stub applications for [cpan://CGI::Application], that sort of thing. If it fills half the screen its probably too long to write without strict. Maybe this just means a lot of my scripts are now less than half a page long, I'm not sure. I just know that it is occasionally easier to just throw caution to the wind. But then I am also very likely to make warnings fatal which for me is a stricter sort of strict - your code ends being *required* to operate on the data sanely or you fall over a fatal runtime error.</p><hr /><p>Added text. I included an example of the sort of thing I'm thinking of. This could be written with strict but why bother? I also wrote [id://265667] without strict or warnings. I added them on at the end just to keep the 'use strict'/warnings people happy.</p><code>#!/usr/bin/perl -T
BEGIN { $root = '/users/greentechnologist.org'; }
use lib $root;
use Camp;
Camp::DataEntry
->new( TMPL_PATH => "$root/Tmpl/",
PARAMS => { DBH_DSN => 'dbi:Pg:dbname=...',
DBH_USER => '...',
DBH_PASS => '...',
DBH_OPT => { RaiseError => 1 } } )
->run;</code>
265561
265600