One word of advice about warnings/strict: These should be used only during the development of a script. Once you release a script to production, you should either remove the "use" statements entirely or comment them out. Commenting may be preferable since, when the inevitable happens--a change request comes in or a bug shows up--it's easier to remember to un-comment it/them during redevelopment than it is to remember to put them back in.
Regards,
Deane
| "yop = me" <[EMAIL PROTECTED]>
Sent by: [EMAIL PROTECTED] 04/30/2004 11:23
|
To: "$Bill Luebkert" <[EMAIL PROTECTED]> cc: active perl <[EMAIL PROTECTED]> Subject: Re: Why use strict |
mmm ...
i can see that i have wroten bad programs for about 4 years.
but why there are bad programs if the scrpts i haved made,
do what it's suposed to do?
for me a bad program is that they dont do what they suposed to do.
or well ... they do the thinks suposed to do, but dosen't use well
the memory of the OS.
or they can easy be destroyed (i mean, not deleting the file of course
:-)) )
now i am writing a script using what $Bill Luebkert told me ...
puting
use warnings; # or -w switch
use strict;
in the top of my script
and i still don't uderstand well, but i begin to feel as part of the PerlSet
(just like jetset) :-))
----- Original Message -----
From: "$Bill Luebkert" <[EMAIL PROTECTED]>
To: "yop = me" <[EMAIL PROTECTED]>
Cc: "active perl" <[EMAIL PROTECTED]>
Sent: Friday, April 30, 2004 10:37 AM
Subject: Re: Why use strict
> yop = me wrote:
>
> > Hi
> >
> > Perl and i knows us about 4 years.
> > But i am a graphic designer that learn it by my own.
> > i haven seen many scripts (not wroted by me), that
> > have the line use strict; in the top, and one time i read
> > a post that teels me about it.
> >
> > could some one aout there tell me why use this module?
> > but if you can, please remember that i am a graphic designer
> > using Perl, and dont have study it in school ore somthing similar.
> > so please if you have the patience to explain it,
> > use apples and pears to tell me.
>
> These two will keep you from writing bad programs :
>
> use warnings; # or -w switch
> use strict;
>
> It will take you a while to be able to correctly write a
> program using them though. You'll need to declare your
> variables before using them and watch your scoping.
>
> Read perldebtut man page/pod for some more insight on it.
>
> --
> ,-/- __ _ _ $Bill Luebkert Mailto:[EMAIL PROTECTED]
> (_/ / ) // // DBE Collectibles Mailto:[EMAIL PROTECTED]
> / ) /--< o // // Castle of Medieval Myth & Magic
http://www.todbe.com/
> -/-' /___/_<_</_</_ http://dbecoll.tripod.com/ (My Perl/Lakers stuff)
>
> _______________________________________________
> ActivePerl mailing list
> [EMAIL PROTECTED]
> To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
>
_______________________________________________
ActivePerl mailing list
[EMAIL PROTECTED]
To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
_______________________________________________ ActivePerl mailing list [EMAIL PROTECTED] To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
