Maybe consider: use diagnostics;
as well, at least while you are developing your code. Thanks! :-) > Anthony (Tony) Esposito > Senior Technical Consultant > Inovis(tm) > 2425 N. Central Expressway, Suite 900 > Richardson, TX 75080 > (972) 643-3115 > [EMAIL PROTECTED] > -----Original Message----- From: Steve Grazzini [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 24, 2003 2:22 AM To: NYIMI Jose (BMB) Cc: [EMAIL PROTECTED] Subject: Re: Perl Best Practices On Tue, Jun 24, 2003 at 09:17:10AM +0200, NYIMI Jose (BMB) wrote: > Here are some best practices i know: > 1. use warnings or -w > 2. use strict; > > Could you extends the list please ? Those are probably the most important. :-) And from the making-best-use-of-available-resources dept: 3. use perldoc 4. use CPAN -- Steve -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
