On Fri, 25 Jan 2002, Ivor Williams wrote:
> 1. When educating colleagues, pick on the sysadmins. They are a good
> receptive audience for the perl quality argument, especially as it is their
> machines that potentially get cracked. Are there any good Perl books in this
> line?
Perl for system administration isn't half bad (ora.com)
> 2. Can we improve on perl's innate ability to detect bad code (use strict;
> taint, perl -w etc.)?
Technical solutions to social problems don't work. Tried this.
> 3. How about an exam with a qualification. The Perl Community could define
> its own without relying on vendors with alterior motives.
Too big. Think small, but with wide ranging consequence. Good is great,
but done is better. (Speaking as someone who has tried big and always
failed.)
--
s'' Mark Fowler London.pm Bath.pm
http://www.twoshortplanks.com/ [EMAIL PROTECTED]
';use Term'Cap;$t=Tgetent Term'Cap{};print$t->Tputs(cl);for$w(split/ +/
){for(0..30){$|=print$t->Tgoto(cm,$_,$y)." $w";select$k,$k,$k,.03}$y+=2}
